SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
What I would like to do, and it's a pound to a pinch of salt someone here will tell me how, is to run that script automatically, then to somehow have it tagged as having been run, and avoid running it fot the next X number of boots, where X=some arbitrary number I can assign, maybe via a .conf file of some sort.
Anyone any suggestions?
Read the crontab man pages and I think you'll find what you are looking for, e.g.:
# run every day at 11 am, appending all output to a file
0 11 * * * date >> /var/log/date-output 2>&1
Crontab gives an incredibly fine-grained control over running jobs, including being able to check the last time that a job was run, whether it was run successfully or not, etc.
man crontab ;)
Last edited by harryhaller; 09-21-2010 at 04:16 PM.
I've followed the suggestions pointed out in this thread, beside putting in background the start of some daemon I've put part of rc.M into an executable saved in cron.daily like explained by Woodsman obtaining a considerable reduction in boot time. Now I wander if there is a way of knowing if and when this cron's commands are executed … just to be sure that I've done everything properly. Can someone give me instructions?
As root, run 'crontab -l'.
I guess I could do that as well and put all of this in cron daily or weekly, but I can also just run it when it is needed.
No I don't like the Upstart concept. Event driven with rules based on dependencies! I'll pass.
I don't care for the possibility of manually shutting some service down and then finding that it triggers Upstart in to ending something else I didn't necessarily want to stop. The risk and complexity it introduces are simply not worth the 20-40 seconds or so it might save on a boot.
It seems most slack people don't like dependencies. However, there is dependency in our init system. For example, you cannot run rc.M before rc.S. The root cause we have sequence is dependencies between each component.
But I totally agree that introduce a complex core component in order to save 20~30 sec boot time may not be a good trade. Especially for the one who once boot system up would keep it going for days untill *have* to shut it down. But I think for the people who really seeking for extreme boot up time, you can give upstart a try. (BTW, the boot time of Ubuntu *really* impressed me a lot. It feels only seconds to be into a ready desktop)
For systemd, I heard it has been put off untill FC15. Even Fedora people does not accept it, what else can we do?
I have used that house-cleaning stuff. However, there are times when new libs are newly installed but still the system cannot load that shared lib because the updating takes place once a day - if you set the house cleaning daily.
I have rebooted several times but then I discovered that all I need to do is run ldconfig.
It may be annoying to others when it is included in Slackware by default.
All of this work just to shave 30 seconds off the boot time? Unless you're rebooting a couple of dozen times a day at the minimum, is it really worth it? Seriously? Bragging rights for the fastest boot time hardly seems to justify the effort.
I almost never boot. I suspend to RAM whenever I leave the computer for more than 3 minutes, and the wake-up time is about 5 seconds. For me, there's no need to change the init sequence when there are other more useful facilities in modern computers.
I've done a couple of those modifications to shorten boot time but decided it's just not worth it. It is usually an after the fact issue that I remember I have to manually update things that should have been accomplish at boot time.
Besides I like watching the boot messages as they go by.