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 -- -=#| Physics Grad Student & SysAdmin @ U Illinois Urbana-Champaign |#=- -=#| 488 LLP, 1110 W. Green St, Urbana, IL 61801 Ofc:(217)333-0038 |#=- -=#| 4602 Beckman, VMIL/MS, Imaging Technology Group:(217)244-3074 |#=- -=#| <[EMAIL PROTECTED]> www.uiuc.edu/~menscher/ Fax:(217)333-9819 |#=- -=#| The above opinions are not necessarily those of my employers. |#=- _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
