-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks for your answer, it saved me a lot of time, I was starting to examine the source package to guess what was wrong with my config.
Now I know that stop doesn't work so I stop clamd with kill and ps. This tip solved my socket file location problem too. Maybe you should drop a line about that in some README file if this bug is not fixed for next release ? Le Vendredi 12 Mars 2004 14:15, Stephen Gran a écrit : > On Wed, Mar 10, 2004 at 10:52:50PM +0100, Thomas Carrié said: > > Hi, > > > > I'm Debian woody user. I've just setup clamav-daemon from deb > > http://people.debian.org/~sgran/debian woody main > > > > I've choosed the Unix socket file > > > > /etc/init.d# /etc/init.d/clamav-daemon restart > > Restarting clamav daemon: clamd > > Stopping clamav daemon: clamd. > > Starting clamav daemon: clamd/usr/sbin/clamd already running. > > . > > It points out that stop doesn't work > > This is a problem with clamd's signal handling. It is being worked > on, but it is clearly not right yet. When it fails to die, as in this > case, you can do: > ps ax | grep clamd > > kill (the pids you see from the first command) > > > Also I've noticed that the socket unix file is not produced or not in > > the right place : > > > > /etc/init.d# grep ocket /etc/clamav/clamav.conf > > LocalSocket /var/run/clamav/clamd.ctl > > FixStaleSocket > > /etc/init.d# ls /var/run/clamav/clamd.ctl > > ls: /var/run/clamav/clamd.ctl: No such file or directory > > I think if you look at the log file (/var/log/clamav/clamav.log by > default) you will see some explanation of that - might be permissions, > might be that clamd can't create a new socket file because the old > daemon is still running. If it's permissions, you'll have to adjust the > permissions accordingly. If it's because the old daemon is still > running, killing it should allow you to start it again, and it should > write the new socket. > > > I'm unable to use clamav with this problem : I haven't found any > > workaround. Should I just recompile it ? > > Most of the signal handling problem is in the upstream code, so > recompiling the same source won't help much. If you want you can grab a > newer CVS checkout, drop in the debian/ directory, and build new debs > from that. Since they area actively working on the signal handling > issues, it may be fixed by now. > > Hope that helps, and sorry about the delay getting back to you, - -- Thomas Carrié Identité GPG : 0285ED14 http://www.adullact.org/IMG/pdf/doc-157.pdf http://www.lebars.org/sec/tcpa-faq.fr.html http://www.pimientolinux.com/peru2ms/villanueva_to_ms.html http://petition.eurolinux.org/pr/fr/pr17.html http://aful.org/publi/articles/gilmore-copy-protection.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQFAU4TynJNpQgKF7RQRAjAUAJ98hAXKBhT0+ceXiSn0Nc9rOcyTLACdHSwS DcKWRq9aoUU5pW9P/L1nJsE= =JXut -----END PGP SIGNATURE----- ------------------------------------------------------- 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_id70&alloc_id638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
