I was using clamav-0.75.1 with daemontools and a stderr-patch (developed for 0.70 but working on 0.75.1) to catch all the output to multilog. I recently upgraded to clamav-0.80rc3 and I found that when starting the clamd service 2 instances of clamd are running and the log shows me that daemontools tried to start clamd every second. When clamdctl stop only 1 of these instances are killed and clamd continues to run until killall clamd.
This is my clamdctl start section:
[code]
#!/bin/sh
PATH=/opt/clamav/bin:/bin:/usr/bin:/usr/local/bin:/usr/local/sbin
export PATH
case "$1" in
start)
echo "Starting clamd"
if svok /service/clamd ; then
svc -u /service/clamd
else
echo clamd supervise not running
fi
if [ -d /var/lock/subsys ]; then
touch /var/lock/subsys/clamd
fi
;;
[/code]This is my supervise/run script:
[code]
#!/bin/sh
exec 2>&1
exec /usr/local/bin/setuidgid root /usr/local/bin/softlimit -a 40000000 /opt/clamav/sbin/clamd -c /opt/clamav/etc/clamd.conf
[/code]
And finally, this is clamd.conf: [code] LogFile stderr LogSyslog LogFacility LOG_MAIL LocalSocket /tmp/clamd FixStaleSocket MaxThreads 20 User qscand ScanOLE2 ScanMail ScanHTML ScanArchive ScanRAR [/code]
Clamdscan is called from qmail-scanner.
1. Anyone aware of a new patch for outputing to stderr?
2. What am i doing wrong since i cannot start only 1 instance of clamd and daemontools tries to fire-up every second a new proccess although clamav is already up?
Thanks, Arthur _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
