This one time, at band camp, Patrick Cherry said: > Upon starting up, clamav-daemon does not create its pidfile until after the > databases have been loaded. This results in a long period during > which multiple clamav instances can be started.
clamd does not, in and of itself, prevent multiple copies of itself from being started. Any extra copies will fail to do anything, since they can't bind to the listening socket, though, so they're harmless, and should kill themselves off. This isn't going to be fixed for etch - one of the reasons you're seeing long load times is due to some problems fixed much later and only available in volatile or lenny/sid. I would suggest a) upgrading to the version in volatile and b) fixing your process monitor to use something other than the pidfile. -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
