Date: Sat, 17 Feb 2007 16:59:16 -0500 From: Mike Tancsa <mike@sentex.net> To: Francisco Reyes <lists@stringsutils.com> Cc: freebsd-isp@freebsd.org Subject: Re: Clamav replacement for FreeBSD+postfix? Message-ID: <200702172201.l1HM1BnR009915@lava.sentex.ca> In-Reply-To: <cone.1171743956.652183.78181.1000@zoraida.natserv.net> References: <cone.1171556679.453588.55347.1000@zoraida.natserv.net> <i2hat2l2ml6q1bfhv1t8ja63ghu5jdkocv@4ax.com> <cone.1171743956.652183.78181.1000@zoraida.natserv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 03:25 PM 2/17/2007, Francisco Reyes wrote:
>Mike Tancsa writes:
>
>>We found changing the threading lib helped a lot with stability. (ie
>>clamd would be locking up throughout the day under load without the
>>change). Its been stable for over a month this way on our boxes (well
>>over 100K emails daily)
>
>Great. That sound promissing.
>Is this with i386 or amd64?
i386. clamav, spamassassin/mimedefang are all slower on amd64
>>However, in the last day we have seen the daemon exiting with a sig6
>>using the default clamav-devel port.
>
>So it has been dying alltogether?
I think 2 separate things were going on. First, the daemon would
hang without switching to the alternate threading lib. e.g. if you
connect to port 3310 and issue a PING, it would just stall and never
return a PONG.
The other issue only cropped up a few days ago with certain crafted
messages (we are speculating here) causing the daemon to exit on sig 6.
>Which version are you currently running?
>I had tried the very latest experimental port (as of 2/13) and had
>to revert back to a package I had saved from mid 2006.
We were using the dev version and prev release version out of the
ports and have now switched to .90. The problem of the daemon
getting stuck was still there with the default threading lib with
.90. Changing to libthr makes it work just fine.
---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200702172201.l1HM1BnR009915>