On Sat, May 14, 2005 at 06:37:31AM -0400, Stephen Gran wrote: > * Sadly this will blow up upgrades of clamav-milter that _do_ use clamd for > scanning - apt/dpkg sets them up in essentially random order, so it is > equally likely that the milter will get set up first and bail since it > can't connect to clamd. Waiting for the bug reports, but I see no other > way to do this properly. > > Do you see a way to fix this?
I have one machine that uses remote clamd, second uses two: local & remote and third with std configuration ;) Only clean way that I see is to modify clamav-milter so it starts even if no clamd available. Mirek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
