Re: clamAV problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Saturday 14 February 2009 17:35:32 Kai Schaetzl wrote:
> Anne Wilson wrote on Sat, 14 Feb 2009 16:12:47 +0000:
> > > that is userhomedir/tmp/clamd.socket
> >
> > Kai, I'm lost.  That's what I touch'd, so it does exist.
>
> Read again, this is "userhomedir/tmp/clamd.socket" and not
> "/tmp/clamd.socket". clamd does not use the socket
> "userhomedir/tmp/clamd.socket" unless you tell it to do so. And freshclam
> does not try to signal to that socket unless it cannot find the correct
> clamd.conf or has some other problem that you created. Find out why your
> freshclam is trying the wrong socket.
> If you installed clamav from rpmforge, it works out of the box.
> There is nothing needed to be touched, remove that touched file!
> Check your clamd.conf that the correct socket gets used, check
> freshclam.conf that the correct clamd.conf is read and start clamd.
> There's nothing else to do.
> And if you don't need clamd, there's no need to install it or signal to
> it. So, tell it not to signal.
>
"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

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux