Read the crontab man pages and I think you'll find what you are looking for, e.g.:
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.

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.

Does anyone have ever tried upstart or some thing like that?

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.


Interestingly, I was just reading about systemd on lwn.net

It seems very clever, but again, perhaps a little too clever. I'll take slow and reliable.

1 members found this post helpful.

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?

If the tips from here are correct, why don't Pat use it in Slackware by default?

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.

1 members found this post helpful.

I don't know what my boot time is, but it's fast enough for me It was excessively long tho, before I tweaked it.

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.

I haven't timed my boot-up, but it's fast enough for me. I'm not working against the clock, I had enough of that crap when I was working in machine shops on piece-work.

Why brianL, nice to hear you were a machinist -as I once was myself.

Yeah, mostly on milling machines.

The TuxOnIce kernel patch has sped up hibernate quite a bit for me.
http://tuxonice.net/

It only takes about 10 seconds to resume on my netbook with 1 GB ram (it takes about 30 seconds when using the default 'swsusp')