On Tue, 2004-10-19 at 13:27, Alexander Dalloz wrote: > Am Di, den 19.10.2004 schrieb Jens Schmidt um 3:42: > > > sorry i forgot to add the vscan-clamav.conf file. > > The configuration i use is pretty much default. > > The directory /var/run/clamav exists. I added the following permission > > chmod a+rw /var/run/clamav. > > Wrong, give it "chmod 755". > > > But there is no /var/run/clamav/clamd.sock file. Could that be the > > problem? > > Sure, that is the problem. Or how do you think does vscan-clamav > contacts the clamd? > > Find the clamd socket file. Check the /etc/clamd.conf (or ClamAV older > 0.80 it is /etc/clamav.conf) for the configured socket file. > > > Jens > > > > here is the vscan-clamav.conf file > > > clamd socket name = /var/run/clamav > > With information of the proper clamd socket file configure it properly. > Actually it is pointing to the directory of the pid file. This is wrong. > It must be the full, proper path to the clamd socket file. > > Alexander Thanks Alexander, that fixed my problem. I enabled LocalSocket /var/run/clamav/clamd.sock and disabled #TCPSocket 3310 in the /etc/clamd.conf file In /etc/samba/vscan-clamav.conf i have specified the full path to the socket file clamd socket name = /var/run/clamav/clamd.sock Jens -- Jens Schmidt 20 Station St Belgrave, VIC 3160
