On Thu, 31 Oct 2002, Odhiambo Washington <[EMAIL PROTECTED]> wrote >* Tomasz Kojm <[EMAIL PROTECTED]> [20021031 03:06]: wrote: >> On Wed, 30 Oct 2002 17:44:02 +0000 >> Chris Hastie <[EMAIL PROTECTED]> wrote: >> >> > I'm still finding the same problems with trying to close down clamd >> > cleanly. It picks up a TERM signal, the log says it's closing, but the >> > process is left running but not responding and the socket file left in >> > place. >> >> Hmm.. Please try to remove manually the lines 192-193. BTW, does it create >> a core file ? Under -CURRENT seems to work OK. > > >On my 4.7-STABLE boxes I don't have a problem at all. I am running clamd >and also have a cron job that monitors whether it's alive or dead and restarts >it and I haven't had a problem so far. With the script that I sent, I did >several stop|start tests and there was no core dump. > The script you sent is in effect a work around. It is sending a KILL (9) rather than a TERM (15) signal, and then cleaning up the socket file afterwards. I'm using a similar script, but being able to send a TERM signal and have clamd shutdown cleanly would be very much more preferable.
Tomasz, I don't see a core file. I'll have a look at your suggestions later when I have some more time. -- Chris Hastie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
