My clamd process hung today for reasons unknown and took MIMEDefang along with it. There was nothing in any of the clamav logfiles, the hourly database integrity checks just stopped happening and clamd wasn't responding to scan requests... :-(
Since the message_contains_virus_clamd() function doesn't have timeouts, all of the mimedefang processes were stuck waiting for clamd to respond to the PING/PONG sequence until they got killed off by the multiplexor. <repeat> <repeat> <repeat ad nauseum> Attached is a patch which adds a 5-second timeout to the PING/PONG process when talking to clamd. If clamd doesn't respond in that timeframe, the routine now properly returns a "cannot-execute" status. Chris Myers Networks By Design
mimedefang-2.44-clamd.patch
Description: Binary data
_______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
