Damian Menscher wrote:
[6th try to get this sent out.]
And i've seen this messages 6 times already.
I'm using clamav-milter in the default mode (no --external flag). As
such, I
see no need to run clamd. But freshclam doesn't like this very much:
freshclam[26975]: ERROR: Clamd was NOT notified: No socket specified in
/usr/local/encap/clamav-0.83/etc/clamd.conf
Now, clamav-milter will still see the updates, right? Since it checks the
database for changes? Or should I be doing something differently here,
like
setting the socket in clamd.conf to the milter.sock (rather than the
clamd.sock
it would normally have pointed to)? If I'm not doing something wrong here,
then perhaps this freshclam message should be toned down a bit from
ERROR to
Warning, or have a flag to disable it?
Damian Menscher
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
