RE: cron problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Thanks, makes sense.

However, on my home computer, it is more vital that jobs are run when I say they should be run, and not according to a random formula. If the football game starts at 1630, I don't care to be reminded up to 68 minutes afterward :-)

I guess there's no harm in removing that 000-delay.cron job, eh?


Date: Tue, 30 Jan 2007 15:14:26 -0500
From: [email protected]
To: [email protected]
Subject: Re: cron problem

Oftentimes, Cron is used to setup communication with other servers to update Clamav or Spamassassin, maybe to run Yum check-update.
The issue is that if everybody is hitting the servers on the hour, we have instataneous hourly DOS attacks on those servers.
The random delay prevents this by randomizing the access time while guaranteeing that within the next XX minutes you will run the update

On 1/30/07, kwhiskerz kwhiskerz <[email protected]> wrote:
On the weekend an update to cron came out with this new script: /etc/cron.daily/000-delay.cron

What it appears to do is to introduce a random length of delay before cron/anacron run.

What is the point of introducing randomness into a finely tuned system?

When one sets up crontab/anacrontab to go off at precisely a certain time, one expects it to run at the time specified, and not at some random time in the next 68 minutes!

What purpose does this serve?


Stay up-to-date with your friends through the Windows LiveT Spaces friends list. Check it out!

fedora-list mailing list
[email protected]
To unsubscribe:

|O O|  [email protected]
~~~~ Javier Perez
~~~~   While the night runs
~~~~   toward the day...
  m m   Pepebuho watches
    from his high perch.

Live Search: New search found Try it!

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux