I'm wondering why clamd first logs to the clamd.log that the Pid and Socket files were removed, then reports errors that it could not unlink the Pid and Socket files. This happens when the clamd service is stopped (service clamd stop) on Fedora 10, with ClamAV version 0.95rc1.
Wed Mar 4 16:55:16 2009 -> WARNING: Syncpipe write failed Wed Mar 4 16:55:16 2009 -> WARNING: Syncpipe write failed Wed Mar 4 16:55:16 2009 -> Pid file removed. Wed Mar 4 16:55:16 2009 -> --- Stopped at Wed Mar 4 16:55:16 2009 Wed Mar 4 16:55:16 2009 -> Socket file removed. Wed Mar 4 16:55:16 2009 -> ERROR: Can't unlink the pid file /var/run/clamav/clamd.pid Wed Mar 4 16:55:16 2009 -> --- Stopped at Wed Mar 4 16:55:16 2009 Wed Mar 4 16:55:16 2009 -> ERROR: Can't unlink the socket file /var/amavis/clamd.sock I checked after clamd was stopped, and neither the Pid nor Socket files existed, which is probably why they could not be unlinked. Should I open a bug about this or is this a known issue? Bill _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
