At 11:44 AM 12/9/2004, [EMAIL PROTECTED] wrote:
Subject pretty much says it.
for reference, both .75 and .80 were built with the following:
#!/bin/sh
./configure \
--with-gnu-ld \
--with-user=qscand \
--with-group=qscand \
--enable-bigstack \
--disable-clamuko
thanks for the responses, everyone. i
At 01:16 PM 12/10/2004, you wrote:
24038 clamdRET poll 0
24038 clamdCALL gettimeofday(0x2811db18,0)
24038 clamdRET gettimeofday 0
24038 clamdCALL clock_gettime(0,0xbfaedfa8)
24038 clamdRET clock_gettime 0
24038 clamdCALL poll(0x8064000,0xb,0)
24038 clamdR
On Dec 09, 2004, at 14:44, [EMAIL PROTECTED] wrote:
Subject pretty much says it.
running qmail, qmail-scanner, spamassassin.
0.75.1 was built on freebsd 5.2, gcc 3.3.3, and ran for months with
never a hint of unhappiness. no crashes that i ever recall happening.
0.80 was built on freebsd 5.2, gcc
[EMAIL PROTECTED] wrote:
by 'crashes', that includes the clamd process just silently aborting, so
mail starts to pile up on my MX gateways, or other times clamd is
"running", using lots of cpu time, but non-responsive - messages again
start piling up on the MX gateways, unable to be accepted by
Subject pretty much says it.
running qmail, qmail-scanner, spamassassin.
0.75.1 was built on freebsd 5.2, gcc 3.3.3, and ran for months with never a
hint of unhappiness. no crashes that i ever recall happening.
0.80 was built on freebsd 5.2, gcc 3.3.3, five days ago, and crashes many
times a day
