[Pkg-clamav-devel] Bug#577499: Bug#577499: Me too

2010-04-26 Thread Michael Tautschnig
[...] After the 4 dpkg-reconfigure runs, things seem to be working. That was the end result mentioned above. That nothing in /etc/clamav changed after the fresh re-install (after purging) was interesting. It is hard to see the config files as being broken, if they weren't changed

[Pkg-clamav-devel] Bug#577499: Bug#577499: Me too

2010-04-24 Thread Stephen Gran
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

[Pkg-clamav-devel] Bug#577499: Bug#577499: Me too

2010-04-24 Thread Gordon Haverland
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

[Pkg-clamav-devel] Bug#577499: Bug#577499: Me too

2010-04-24 Thread Michael Tautschnig
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

[Pkg-clamav-devel] Bug#577499: Bug#577499: Me too

2010-04-24 Thread Gordon Haverland
On April 24, 2010, Michael Tautschnig wrote: 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