On Tue, 2004-02-17 at 01:22, Lionel Bouton wrote:
Yes
But in the crontab case be aware that the mean time between updates in :
0 * * * * sleep $[ $RANDOM % 3600 ] ; /usr/bin/freshclam --quiet
is 3600s, but between 2 updates the delay can be anywhere between 1 and 7199s.
Computing
I searched the archives, but didn't see an answer so pardon me if
it's a FAQ. How often is it reasonable to call freshclam (either
from cron or in daemon mode) to check for new virusdb updates?
Obviously there's a tradeoff between detecting fast spreading
viruses like MyDoom and overloading the db
Bill Randle wrote the following on 02/16/2004 10:12 PM :
I searched the archives, but didn't see an answer so pardon me if
it's a FAQ. How often is it reasonable to call freshclam (either
from cron or in daemon mode) to check for new virusdb updates?
Obviously there's a tradeoff between detecting
On Mon, 2004-02-16 at 16:35, Lionel Bouton wrote:
Once an hour is fine, but if you use crontab please add a once randomly
chosen sleep between 0 and 3599 second before launching freshclam.
As lots of people using crontab put something like 0 * * * * ... The
database mirrors have huge peaks
On Mon, 2004-02-16 at 15:11, Luke Scharf wrote:
On Mon, 2004-02-16 at 16:35, Lionel Bouton wrote:
Once an hour is fine, but if you use crontab please add a once randomly
chosen sleep between 0 and 3599 second before launching freshclam.
As lots of people using crontab put something like 0
Luke Scharf said:
This does seem more polite than hitting it hard, right on the hour.
-Luke
--
Luke Scharf, Systems Administrator
Virginia Tech Aerospace and Ocean Engineering
If you use freshclam as a daemon, you don't have to worry about this as it
randomizes it?
--
Luke Computer
Lucas Albers wrote the following on 02/17/2004 01:17 AM :
Luke Scharf said:
This does seem more polite than hitting it hard, right on the hour.
-Luke
--
Luke Scharf, Systems Administrator
Virginia Tech Aerospace and Ocean Engineering
If you use freshclam as a daemon, you don't have to
