Benjamin Franz wrote: > On 05/10/2010 01:30 PM, Les Mikesell wrote: >> On 5/10/2010 2:51 PM, Benjamin Franz wrote: >>> Actually, they do (break when updating, that is). >>> >>> The problem is at least one of the packagers for clamd/amavisd-new >>> blindly overrides the path to clamd.sock by overwriting the config file >>> leaving the two out-of-sync (and so unable to function). >>> >>> It is easily fixed by resetting the path - but you do have to watch out >>> for it on upgrades. >>> >> Is this a result of having multiple uncoordinated 3rd party repositories >> enabled during an update and flipping repositories as the version >> numbering jumps (more or less expected behavior...) or are you saying >> that a single packager flipped the format in an incompatible way? >> >> > This is using rpmforge/Dag (only). That is the only 3rd party repo I use > for my production systems. Updates of clamd has replaced /etc/clamd.conf > twice on me in the last year or two, each time breaking my mail system > until I fixed it. Most recently in April of this year. > Should I be worried if the only clamd.conf on the mail server is in /usr/share/doc? Virus scanning is working.