>>You can try the util "clamdscan" (NOT clamscan) which will contact clamd<br>>>to have files scanned.<br>>>If that works your clamd is alive. If it says something along<br><br>>>connect(): No such file or directory<br>
>>WARNING: Can't connect to clamd.<br><br>>>then your clamd is broken.<br>>>Try starting it with<br><br>>$> /etc/init.d/clamd start<br><br>>clamdscan works fine, but I am still getting the following errors, and mailwatch shows zero viruses, even though tailing maillog shows viruses are discovered. Spent most of two days on this >now:( Nothing gets logged to clamd.log unless I start it manually. Clamav.log shows nothing. Clamav is owner of both logss.<br>
<br>>May 16 14:40:27 relay-1 MailScanner[3889]: ERROR:: COULD NOT CONNECT TO CLAMD, RECOMMEND RESTARTING DAEMON<br>>May 16 14:40:27 relay-1 MailScanner[3750]: Clamd::ERROR:: COULD NOT CONNECT TO CLAMD, RECOMMEND RESTARTING DAEMON :: .<br>
>May 16 14:40:27 relay-1 MailScanner[3750]: Virus Scanning: Clamd found 1 infections<br><br clear="all">I have to change my /etc/clamd.conf to "LocalSocket /tmp/clamd" (or "Clamd Socket = /tmp/clamd.socket" in the MailScanner.conf) so MailScanner can find Clamd via the socket file. Run "MailScanner --lint" before you do anything and note any clam errors. Then make the edit, restart clamd and run "MailScanner --lint" again to see if everything is happy after the change.<br>
<br>-- <br>Dave Jones