We're setting up a new MX server and have built clam from the .gz file.
We then copied over the clamd.conf file from a working system.
Here's the problem: When we start clamd, it creates
/var/log/clamav/clamd.log with root ownership. This causes grief for
clamav-milter.
# /sbin/service clamav-milter start
Starting clamav-milter: /var/run/clamav/clamd.sock: No such file or
directory
Can't talk to clamd server via /var/run/clamav/clamd.sock
Check your entry for LocalSocket in /etc/clamd.conf
[FAILED]
However, clamd is properly running under the ID "clamav" as specified in
/etc/clamd.conf.
If I change ownership of clamd.log to clamav:clamav, clamav-milter is
happy until the logs roll on monday morning.
What am I missing?
From clamd.conf:
# Run as a selected user (clamd must be started by root).
# Default: disabled
User clamav
from ps:
clamav]# ps -ef |grep clam
clamav 13824 1 0 17:48 ? 00:00:00 /usr/sbin/clamav-milter
-l --external --quiet --max-children=20 --dont-log-clean
local:/var/run/clamav/clamav-milter.sock --quarantine-dir=/var/spool/clamav
clamav 14109 1 0 18:03 ? 00:00:00 /usr/sbin/clamd
root 14188 22886 0 18:11 pts/3 00:00:00 grep clam
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
