On Thu, 04 Dec 2003 22:13 , Thomas Lamy <[EMAIL PROTECTED]> sent:
>McKeever Chris wrote: > >> # clamdscan --version >> clamdscan / ClamAV version 0.65 >> >> >> ]# clamdscan >> connect(): No such file or directory >> ERROR: Can't connect to clamd. >> >> ----------- SCAN SUMMARY ----------- >> Infected files: 0 >> Time: 0.001 sec (0 m 0 s) >> >> >> any ideas? clamav.conf file? or permissions issues? >> >I suggest clamav isn't running, as the config file (and thus the >LocalSocket configuration parameter) is read by both clamd and >clamdscan. Or you changed that paramter after starting clamd. good call, noticed that clamd dies after running for a bit. I think I have some configs wrong..but that is the case.. thanks ------------------------------------------- Chris McKeever If you want to reply directly to me, please use cgmckeever--at--prupref---dot---com http://www.prupref.com ---- Prudential Preferred Properties www.prupref.com ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
