I am suffering the same problem, I'm running SuSE 9 Pro. Typing 'clamd' gives no response whatsoever,
Again, how do you get your package (rpm, source, binary .tar.gz, etc)? Next, find out where your clamav.conf is. There sould be a line similar to
LocalSocket /tmp/clamd ==> The location of your socket LogFile /usr/local/share/clamav/clamd.log ==> clamd log file
You might use syslog for clamd instead of LogFile. In that case, to help debugging,
add LogFile line to clamav.conf. Make sure that file/directory is writable by clamav user.
Then, start clamd and see what your clamd.log says. A successful start would have
these entries :
Tue Mar 16 16:12:15 2004 -> +++ Started at Tue Mar 16 16:12:15 2004
Tue Mar 16 16:12:15 2004 -> Log file size limit disabled.
Tue Mar 16 16:12:15 2004 -> Running as user root (UID 0, GID 0)
Tue Mar 16 16:12:15 2004 -> Reading databases from /usr/local/share/clamav
Tue Mar 16 16:12:15 2004 -> Protecting against 20350 viruses.
Tue Mar 16 16:12:16 2004 -> *Unix socket file /tmp/clamd*
Tue Mar 16 16:12:16 2004 -> Setting connection queue length to 30
Tue Mar 16 16:12:16 2004 -> Archive: Archived file size limit set to 10485760 bytes.
Tue Mar 16 16:12:16 2004 -> Archive: Recursion level limit set to 5.
Tue Mar 16 16:12:16 2004 -> Archive: Files limit set to 1000.
Tue Mar 16 16:12:16 2004 -> WARNING: USING HARDCODED LIMIT: Archive: Compression ratio limit set to 200.
Tue Mar 16 16:12:16 2004 -> Archive support enabled.
Tue Mar 16 16:12:16 2004 -> RAR support disabled.
Tue Mar 16 16:12:16 2004 -> Mail files support disabled.
Tue Mar 16 16:12:16 2004 -> OLE2 support disabled.
Tue Mar 16 16:12:16 2004 -> Self checking every 3600 seconds.
Tue Mar 16 16:12:16 2004 -> ERROR: Clamuko is not available.
clamscan has installed and is functional.You don't need clamav-milter for amavisd-new. Just read amavisd-new docs or config file,
My symptoms are the same.
What do I need to do I have read as much info as I can get hold of. Would clamav-milter installation improve the situation.
I'm using amavisd-new to tie everything together, spamassassin is working fine.
see where it expects clamd to be (path to local socket, or TCP port) then change
your clamav.conf to match it. It might help if you run clamav as the same user as amavis
(e.g change User line on clamav.conf).
Regards,
Fajar
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
