|
|
Please CC the bug when replying. That way the official record and the
maintainer also receive your mail.
[Reply below, leaving full mail quoted for the BTS]
On Thu, 2004-09-30 at 21:01, Dustin Lundquist wrote:
> Adam,
>
> I noticed that freshclam's logs did not show any check in the few weeks
> on two separate servers running sarge, the man page says:
> -d, --daemon
> Run in a daemon mode. This option requires --checks.
> So I added a -c option to the command line in
> /etc/init.d/clamav-freshclam, now freshclam is logging checks. Here is
> an exert of the log displaying the gap:
> Received signal 14, wake up
> ClamAV update process started at Tue Aug 10 14:26:40 2004
> main.cvd is up to date (version: 24, sigs: 21793, f-level: 2,
> builder:
> tomek)
> daily.cvd is up to date (version: 447, sigs: 1542, f-level: 2, builder:
> trog)
> --------------------------------------
> Received signal 14, wake up
> ClamAV update process started at Tue Aug 10 16:26:42 2004
> main.cvd is up to date (version: 24, sigs: 21793, f-level: 2, builder:
> tomek)
> Received signal 1, re-opening log file
> --------------------------------------
> ClamAV update process started at Thu Sep 30 09:47:58 2004
> main.cvd updated (version: 27, sigs: 23982, f-level: 2, builder: tomek)
> daily.cvd updated (version: 510, sigs: 636, f-level: 2, builder: trog)
> Database updated (24618 signatures) from database.clamav.net
> (64.69.64.158).
> Clamd successfully notified about the update.
> It's possible that something else caused freshclam to stop doing check,
> but if so I'm not seeing it.
>
> Thanks,
>
> Dustin
Hmmm, very strange. If that's the complete log file then it looks like
the 16:26 check on August 10th never got as far as checking daily.cvd,
which would lead me to suspect something strange occurred.
Certainly our locally built packages (a woody backport) don't use -c and
looking back through the logs I can't see any evidence of the checks
having stopped.
Signal 1 is SIGTERM, which I'd expect to see on a log rotation. Is it
possible that the logs were broken after a rotation and adding the extra
argument and restarting the daemon simply fixed the symptom?
That's all the ideas I've got at the moment, Stephen (the maintainer)
may have others.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
|
|