This one time, at band camp, Rick Friedman said: > On Friday 12 August 2005 11:49 am, Stephen Gran wrote: > > This one time, at band camp, Rick Friedman said: > > > When the init script (/etc/init.d/clamav-daemon) runs with the "stop" > > > parameter, the script runs to completion with no errors. However, the > > > clamd process is not stopped. It is still running after the script has > > > completed. Below is output from the script (with set -x in the script). > > > > Can I see the contents of your clamd.conf, please? > > After seeing your request, I checked clamd.conf myself. I found the following: > > # This option allows you to save a process identifier of the listening > # daemon (main thread). > # Default: disabled > # PidFile /var/run/clamd.pid > > I uncommented the PidFile line. That seems to have fixed the problem. Now the > init script stops the clamd process properly. > > The only question I now have is why is the PidFile line disabled by default?
Er, if you take the default, clamd.conf is managed by debconf, and you would have a PidFile directive. The problem is that I recently switched to the lsb-base init script functions, which don't work (currently) without a pidfile. I have submitted a bug with patch to the lsb-base maintainers asking them to also kill instances of the daemon in the absence of a pidfile. I will keep this bug open until lsb-base is fixed, as it will continue to affect clam until then. Thnaks for reporting, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
