On Mon, 23 Feb 2009 07:52:39 -0500
Jerry <[email protected]> wrote:
> There has been an on going discussion regarding the crashing of clamd
> when used with unofficial Clamav definition files. Personally, I am of
> the opinion that a probable cause could be the collision of a secondary
> script with the 'freshclam' daemon.
Actually, the reason of crashes with unofficial signatures is still unknown
as we're not able to reproduce the problem.
> {IDEA ONE}
>
> Having another setting that would allow specifying how many minutes
> past the hour freshclam should run would prove to be a useful addition.
> The say "HR_DELAY" would be off by default, thereby using the same
> protocol as is presently in force. Setting the variable would allow
> forcing the daemon to run at a specific time in relation to the "Check"
> variable. This would then allow users to stagger the running time of
> this daemon and any secondary script that is being used to supplement
> the Clamav database.
You can do it with cron; there's no point in reinventing the wheel and
implementing a scheduler within freshclam
> {IDEA TWO}
>
> Using another variable to indicate whether freshclam should run on odd
> or even hours only. Unfortunately, this would not work for those who
> have 'Check' set to '24'. Actually, I believe that is excessive anyway;
> however, it is not my call.
As above. BTW, it's recommended to run freshclam at least each hour.
Regards,
--
oo ..... Tomasz Kojm <[email protected]>
(\/)\......... http://www.ClamAV.net/gpg/tkojm.gpg
\..........._ 0DCA5A08407D5288279DB43454822DC8985A444B
//\ /\ Mon Feb 23 14:09:22 CET 2009
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
