I am having a problem running clamd with supervise.
Actually, it does this without supervise.
It seems to run, then kill itselfs and daemonise itself.
Then subsequent clamd's uses it as its parent instead on supervise
This started after I upgraded to the latest CVS version, so I have fiddled and
am sure I have done something wrong...
Running before 0.8 CVS:
root 190 173 0 Jan06 ? 00:00:00 supervise clamd
qscand 191 190 0 Jan06 ? 00:00:02 /usr/sbin/clamd
After my fiddling:
root 18898 20172 0 12:07 pts/0 00:00:00 supervise /var/clamav/
supervise/
qscand 18900 1 0 12:07 ? 00:00:00 /usr/local/sbin/clamd
qscand 18909 18900 0 12:07 ? 00:00:00 /usr/local/sbin/clamd
My run:
[EMAIL PROTECTED] clamd]# cat run
exec 2>&1
CLAMD_FILE=/var/clamav/clamd.sock
SCAN_FILE=$0
# Check for a leftover socket.
if [ -e $CLAMD_FILE ]
then
echo "run: WARNING: file $CLAMD_FILE exists"
if clamdscan $SCAN_FILE
then
echo "run: FATAL: Clamd is already running. Trying to start anyway..."
else
echo "run: INFO: Clamd is not running. Deleting $CLAMD_FILE"
rm -f $CLAMD_FILE
fi
fi
# Run the scanner daemon.
exec /usr/local/sbin/clamd
Thanks,
Shaun Bugler
Ps: Forgive me is nothing makes sense, complete clamav noob
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
