Re: Cron
Tom wrote:
[...]
Or, thinking a bit, why not alloc 1440 bits, and once a day process
all the files, setting a bit for which minute to wake up, and when I
wake up, walk forward for the next set bit, and sleep that many minutes?
Do it all again if the files change...
So you have to monitor file-changes which is quite expensive.
And you have to monitor changes to /etc/cron.d* which is even more
expensive.
When will that 'dayly process' which does the calculations run? What
happens if the computer is down at that time?
So like you said: Much work, little (or negative) gain!
You will probably need more resoures than without 'optimization' :)
Stefan
Reply to:
- References:
- Cron
- From: Russell Shaw <rjshaw@iprimus.com.au>
- Re: Cron
- From: Howell Evans <gevans1@utk.edu>
- Re: Cron
- From: "Stefan Waidele jun." <Stefan@Waidele.net>
- Re: Cron
- From: tb.nospam@comcast.net
- Re: Cron
- From: Ron Johnson <ron.l.johnson@cox.net>
- Re: Cron
- From: Tom <tb.nospam@comcast.net>
- Re: Cron
- From: Tom <tb.nospam@comcast.net>