Ian Abbott wrote:
[snip]
It might be the problem, especially if you are sending a signal
(SIGHUP) to the freshclam process from a log rotation script. If this
occurs almost immediately after an internally generated SIGALRM, it
could cause the main loop to terminate early, though that is extremely
unlikely as the time window is very small. A far more likely cause is
that the process is woken up by the SIGHUP and then the internally
generated SIGALRM occurs later, killing the process. The program uses
the default SIGALRM handler while it is doing all the network stuff,
for example, so if the process is woken by an external SIGHUP, spends
a lot of time doing network stuff, and receives the internally
generated SIGALRM at this time, the process will be killed.
I'll mention my theory on the devel list, anyway.
thanks a lot. As far as I know there is no external SIGHUP involved; no
specific log file rotation or whatever. But, as the problem does exist,
I welcome the fact that someone is delving into the code to see whether
there are any possible problems.
Regards,
/rolf
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
