Anne Wilson wrote:
"Clamd successfully notified about the update."
I hate being beaten! :-) I simply removed the line that mentioned a local socket. So simple, and so easily missed. Yes, it probably wasn't enabled by default, but by misunderstanding.
Thanks to all who helped.
Anne
Anne,
Just for the record, I just installed the base packages of clamav, clamav-db using the rpmforge repo on a test machine. The option ...
# Send the RELOAD command to clamd. # Default: no NotifyClamd /etc/clamd.conf
Is enabled by default. So you did by no means break it. That is it's expected behavior. Also please not that in /etc/cron.daily/freshclam you will have the same option enabled, as follows
/usr/bin/freshclam \ --quiet \ --datadir="/var/clamav" \ --log="$LOG_FILE" \ --log-verbose \ --daemon-notify="/etc/clamd.conf"
So no you did not break it. it was turned on by default.
Brian
-- http://wx.Tatorz.com Open WebMail Project (http://openwebmail.org)
Mail List wrote on Tue, 17 Feb 2009 06:41:27 -0500:
So you did by no means break it.
She broke it by changing the path for the socket. ;-)
Kai
On Tuesday 17 February 2009 12:31:18 Kai Schaetzl wrote:
Mail List wrote on Tue, 17 Feb 2009 06:41:27 -0500:
So you did by no means break it.
She broke it by changing the path for the socket. ;-)
Yes. I had understood that I had to give it a suitable place for a local socket. It was, of course, totally unnecessary. When I realised that a socket existed in /var it seemed well worth trying simply commenting the line out. Bingo! A plain misunderstanding on my part.
The help I got on this list prompted me to look in the right places for clues. That's more valuable than a simple instruction that cures it :-)
Thanks again, all
Anne
-
Anne Wilson -
Kai Schaetzl -
Mail List