On 12/26/06 9:16 AM, "Dennis Peterson" <[EMAIL PROTECTED]> wrote:
> We found different solutions. But in nearly 30 years of doing this every > day I can tell you I've never had a cron daemon fail I saw one human-induced (the boss, not me) crond failure on BSDi many years ago. The boss accidentally set the date ahead to 2028 or some such year. He saw his error and set it back appropriately. But crond had noticed, and seemingly was patiently waiting for its next action in 2028. I noticed that I didn't get one of my periodic email reports, and restarted crond. Other versions of cron may well behave better in that situation. Other than that--and Linux running in slow time (known APIC problem on dual processor machine), which is hardly cron's fault--I too haven't seen cron fail. --John _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
