On 5/24/2012 12:29 AM, Paul Wise wrote:
On Tue, 2012-05-22 at 01:09 -0500, Richard Laager wrote:
Why should clamav-unofficial-sigs be the clamd watchdog? If clamd is
actually being used, its caller can (and almost surely will) throw
errors. I run clamd on (some) servers as well, so I'm familiar with
those use cases too.
I'm not sure why Bill made it do that, perhaps he can tell us (CCed)?
Bill, Richard is proposing that I change the configuration of
clamav-unofficial-sigs in Debian so that it detects if clamav-daemon is
running and only then issue reload commands. This will of course break
the clamd watchdog feature of clamav-unofficial-sigs, any thoughts?
http://bugs.debian.org/672537
Whether the clamd status check is enabled in the script or not is up to
the user. There is a variable in the config file that enables the
status check, but is disabled by default:
# If running clamd in "LocalSocket" mode (*NOT* in TCP/IP mode), and
# either "SOcket Cat" (socat) or the "IO::Socket::UNIX" perl module
# are installed on the system, and you want to report whether clamd
# is running or not, uncomment the "clamd_socket" variable below (you
# will be warned if neither socat nor IO::Socket::UNIX are found, but
# the script will still run). You will also need to set the correct
# path to your clamd socket file (if unsure of the path, check the
# "LocalSocket" setting in your clamd.conf file for socket location).
#clamd_socket="/var/run/clamd.socket"
And this is from the script:
# If ClamD status check is enabled ("clamd_socket" variable is uncommented
# and the socket path is correctly specified in "User Edit" section above),
# then test to see if clamd is running or not.
Paul, have enabled this status check as the default setting in the
Debian distro?
Bill
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
