Robert Isaac wrote:
There was only one instance running. Killed it and restarted it. Then in
today's LogWatch:
**Unmatched Entries**
clamd shutdown failed
clamd daemon 0.88.7 (OS: linux-gnu, ARCH: i386, CPU: i386) Bound to address
127.0.0.1 on port 3310 clamd startup succeeded Portable Executable support
enabled.
Detection of broken executables enabled.
Mail: Recursion level limit set to 64.
HTML support enabled.
Bob
Did you happen to notice if the PID of the new process was different
than the earlier PID? Is the PID of the current process the same as in
the clamav.pid file as defined by the clamd.conf PidFile definition? The
reason I ask is that sometimes this location gets changed between the
startup/shutdown script and the clamd.conf script and the script tries
to kill the wrong process, or can't find a process identified in the
clamav.pid file. Just a thought. In any event, check the script and
clamd.conf to be sure they're both looking at the same pid file.
dp
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
