| On Tuesday, 6 January 98, at 2:28:26 AM | Joey wrote about "cron jobs more often than daily" > Steve Greenland wrote: >> Disadvantages: Limited control by packages over granularity, offset, and >> user. (I'm not convinced that this is a real showstopper: if the package >> *really* requires that fine of control, it probably needs a custom user >> anyway.)
> Another disadvantage is that this would lead to run-parts running evey > 5 minutes and wasting some cpu time, even if there were no 5 minute > granularity cron jobs installed on the system. Or: Have a directory, /etc/debian.crontab/, that holds a file for every package that wants to be run by cron. Modify /etc/cron.tab(in the master version), to have a line that runs /etc/init.d/debian.cron. Have a script, update-debian-crontab, that when called to add a new /etc/debian.crontab/package, updates /etc/init.d/debian.cron to run the package that would next need to be. Everytime that /etc/init.d/debian.cron is run, it checks to see when the next package is to be run, and updates itself, and /etc/cron.tab. Does anyone understand what I am trying to accomplish here? Each time /etc/init.d/debian.cron runs, it modifies /etc/cron.tab, changing the time that it will next be run at. This might be better handled with some type of alarm program, that will exec another program at a specific time, instead of every so often. Why do keyboards get replaced? Because people run Windows, and they can't hit Bill! Adam Heath of Borg-Linux [EMAIL PROTECTED] Join the H.323 effort. Email http://www.debian.org - Get Your Own Linux! [EMAIL PROTECTED] with http://wwp.mirabilis.com/3375265 - Page Me the word subscribe in the body. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
