On Monday, September 18, 2006 at 12:10 PM, Nigel Horne wrote:
> > 4) freshclam running at the start of the ClamAV service is nice,
but
> > I'd really hope that the system running ClamAV wouldn't reboot or
> > restart the ClamaAV service very often. Meanwhile, there have been
> > virusdb updates for the last few days which have ranged from a
minimum
> > of 4 up to 8 times per day, so clearly continuously running
freshclam is
> > desirable. What are your plans regarding getting both clamd and
> > freshclam running in the background?
>
> The latest freshclam now supports the --daemon mode, and the latest
> PowerTools from www.bandsman.co.uk/clamav.htm make use of this
facility.
This seems to work, and is a big step forward! Thanks!
Meanwhile, now the freshclam process doesn't get stopped when the ClamAV
service is stopped, and ANOTHER freshclam process is started each time
the ClamAV service is started. Stopping these freshclam processes
requires either rebooting the system or the use of an externally
acquired tool (tkill.exe from the windows resource kit, or a tool from
sysinternals.com (pskill, or procexp)).
When the ClamAV service is stopping, you might want to try cleanly
stopping freshclam with:
GenerateConsoleCtrlEvent(CTRL_C_EVENT, dwProcessId);
Where dwProcessId is the process ID of the freshclam process saved when
the process was created.
- Mark Pizzolato
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32
