This one time, at band camp, Mikolaj Menke said: > Very often clamdscan fails to connect to clamd giving false sense of > security, as nothing is reported, even when the scanned data is infected.
st...@vancouver:~$ clamdscan bin/ connect(): Connection refused WARNING: Can't connect to clamd. I can't reproduce this description of how it works. > This also causes other problems for example with exim4, because when it > encounters this problem it temporarily rejects the message. I could not > find any relevant data neither in the logs nor in the verbose output of > clamdscan. The only interesting thing is in exim4's log: > > 2009-02-17 18:37:49 1LZTtF-0007M6-1a malware acl condition: clamd: \ > unable to write to socket (Broken pipe) Well, that's the opposite of what's described above, surely? That's exim noticing that clamd has gone away and not giving a false sense of security? I am going to suppose that what this bug report is really about is that sometimes clamd is unavailable, and things go wrong, although I can't reproduce the first example and the second example looks like everything being handled as it should. Can you quantify "very often" ? I certainly don't see it that often, but if you do, there's probably something we should be chasing down. Cheers, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [email protected] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
_______________________________________________ Pkg-clamav-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-clamav-devel
