On Tue, 2004-09-07 at 04:19, Matt wrote:
> Ralph Angenendt wrote:
>
> > Niek wrote:
> > > On 9/7/2004 9:28 AM +0200, Ralph Angenendt wrote:
> > >
> > > >Which would give the following behaviour how?
> > > >
> > > >| ClamAV update process started at Tue Sep 7 07:08:22 2004
> > > >| ClamAV update process started at Tue Sep 7 08:01:43 2004
> > > >| ClamAV update process started at Tue Sep 7 08:55:03 2004
> > > >
> > >
> > > something like the following in freshclam.conf:
> > > Checks 25 or 26
> >
> > As you can see, I'm fully aware of that. "How do you do that with
> > crontab" was the question longing for an answer.
> >
> > Ralph
>
>
> There was a crontab entry posted a while since, which made use of
> $[RANDOM] to alter the update time.
>
> Relevant section from the original email:
>
> > As per discussions on this list on awhile ago; I use the following for
> > my crontab entry:
> >
> > 0 * * * * sleep $[ $RANDOM % 1800 ] ; /usr/local/bin/freshclam --quiet
> >
> > this causes it to sleep for a random period of time not exceeding
> > 30 min before executing.
> >
> > Rob
>
>
> Matt
Slightly better, I think, is to add an offset to avoid hitting close to
the hour. This is what I use:
sleep $[ 900 + $RANDOM % 1800 ]
which goes from 15 past to 15 to the hour.
-Bill
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
