On April 24, 2010, Stephen Gran wrote: > This one time, at band camp, Gordon Haverland said: > > with the dfsg-2 update that came out, I seen LocalSocketGroup > > 20 thing with my computer. I set it to 125 (which is the > > group clamav is on this computer). Clamav started, but I > > started getting messages from freshclam (cron jobs) about > > some missing argument. Trying to fix things, I then got a > > message about freshclam not being able to contact clamd via > > /var/run/clamav/clamd.ctl. > > > > So, this morning, I purged all of clamav and reinstalled it. > > This message about clamd.ctl persists. > > Can you set LocalSocketGroup to clamav in the config file, run > dpkg-reconfigure and see what it is in the file afterwards?
LocalSocketGroup was already set to clamav, and the mode is 666. dpkg-reconfigure for clamav didn't appear to do anything, no files altered in /etc/clamav dpkg-reconfigure clamav-base asked questions, no files changed. dpkg-reconfigure clamav-daemon asked questions, no files changed. dpkg-reconfigure clamav-freshclam asked questions, no files changed. It appears that freshclam updated properly, and was able to contact the daemon as part of how dpkg-reconfigure finished for freshclam. It would seem that the reconfigures did something, but none of the changed were in /etc/clamav. Want me to purge, reinstall and check something else? Gord -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org