On Mar 1, 2008, at 4:52 PM, Gary V wrote: > >> Subject: [Clamav-users] serious weirdness on debian etch5> > this >> started last night...> > clamav-daemon wasnt running anymore> > >> restart and it seemed to work> > except local socket and pid file >> werent created.> > tried updating to latest debian version ( we do >> updates first monday > of month ).> restarted, still nothing.> > >> the clamd process runs> but the local socket and pid file dont get >> created.> > log file shows no errors.> > user has permissions >> needed to write to directories in question.> > i'm at a total loss >> here.> > i see a posting in the archives with same issue from feb 4 >> of this year> but no resolution. > > If you are using 0.90.1 (run 'apt-cache policy clamav' to verify > version), it's a known issue that 0.90.1 can take several minutes (I > have heard of up to 15) to create a clamd socket. The fix is to > upgrade. The easy way to do it is to install from etch volatile. > > I suggest adding the etch volatile source to /etc/apt/ > sources.list:deb http://volatile.debian.org/debian-volatile etch/ > volatile mainThen:gpg --keyserver subkeys.pgp.net --recv-key > BBE55AB3gpg --armor --export BBE55AB3 | apt-key add - apt-get > updateapt-get install clamav clamav-daemon clamav-freshclam(an any > other modules you may need). At least, this is how I would do it. > YMMV. > > If you are already using latest version from volatile, then I dunno. > Gary V
Thanks Gary, an upgrade was indeed what was needed. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
