Karl Pielorz wrote:
We've narrowed this down a bit - and it doesn't look like it's just an issue with 0.88.4 - we backed the server down to 0.88.1 and the same thing happened...
As has been noted on this list, the 0.8x series is 'old' code. As such, you may wish to try out clamav-devel from ports--it's (currently) a snapshot from CVS from early(ish) August.
At the moment, we're running it in production on a trio of scanning servers which are being fed by clamav-milter on a pair of border SMTP servers. Running clamd on other external servers provides for redundancy in case one or two clamds pack it in--the milter will still pass messages to the remaining one(s). Everything has actually been stable running the snapshot, though we do run watchdogs to restart clamd in case of failure.
Even if you don't have dedicated scanning servers, if you have multiple SMTP servers, then running clamd in TCP mode bound to an external interface (appropriately firewalled, of course) and setting up clamav-milter to talk to the local clamd as well as the clamds on the other SMTP servers would allow scanning to continue in the event of any local failure.
You don't mention what version of FreeBSD you're running; it may not matter, but the SMTP and scanning servers we run are 6.1-STABLE.
Craig. ------ _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
