The status request simply fails because in /etc/rc.subr ...
status)
if [ -n $rc_pid ]; then
echo ${name} is running as pid $rc_pid.
else
echo ${name} is not running.
return 1
fi
;;
there's only a check whether the pid specified in ...
/usr/local/etc/clamav-clamd.sh
... exists.
After doing a portupgrade of clamd from 0.81 to 0.83, the service reports
that it is not running using 'clamav-clamd.sh status'.
esmtp# cd /usr/local/etc
esmtp# rc.d/clamav-clamd.sh status
clamav_clamd is not running.
esmtp# ps -ax|grep clam
781 ?? Ss 0:10.96 /usr/local/sbin/clamd
Usually if you are running ClamAV in UNI domain socket mode,
there should be a UNIX domain socket called 'clamd' in ...
- /var/run/clamav
Tho - this file can be configured in /usr/local/etc/clamd.conf.
If ClamAv is running in TCP/IP mode it should be possible to
test whether the server is
I do not have anything in /var/run/clamav and that is the location in
clamd.conf for placing the PID file. I cannot connect to the localhost as
well:
esmtp# telnet localhost 3310
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
telnet: connect to address
I think the following section in /usr/local/amavisd.conf
should answer your question:
### http://www.clamav.net/ - backs up clamd or Mail::ClamAV
['ClamAV-clamscan', 'clamscan',
--stdout --disable-summary -r --tempdir=$TEMPBASE {}, [0], [1],
qr/^.*?: (?!Infected Archive)(.*) FOUND$/
Robert Fitzpatrick wrote:
After doing a portupgrade of clamd from 0.81 to 0.83, the service
reports that it is not running using 'clamav-clamd.sh status'.
esmtp# cd /usr/local/etc
esmtp# rc.d/clamav-clamd.sh status
clamav_clamd is not running.
esmtp# ps -ax|grep clam
781 ?? Ss 0:10.96
Thanks, that explains why postfix is still logging. But clamd is running...
esmtp# ps -ax | grep clam
26441 ?? Ss 0:00.37 /usr/local/sbin/clamd
26467 ?? Is 0:00.00 /usr/local/bin/freshclam --daemon
26494 ?? Is 0:00.00 /usr/local/bin/freshclam --daemon
But still the server thinks
