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 3.3.3, five days ago, and crashes many times a day.
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 the spam/virus proxy that clamd is running on.
i noticed a mention in the archives that Jason Haar found that running clam outside of softlimit seemed to cure his problem with clamd hitting memory limit and going into a loop (this is from memory, hopefully i'm not mangling it). i tried this, and while the crashes lessened, i still found clamd "running" but stuck and not processing data this morning.
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
help?
Paul Theodoropoulos
try the following commands in terminal.
./configure --prefix=/usr --mandir=/usr/share/man --sysconfdir=/etc --enable-bigstack --with-user=qscand --with-group=qscand --with-libcurl --with-gmp --enable-readdir_r
I also recommend enabling prebinding before building, enabling this is different for different types of terminal apps, you can use 'setenv LD_PREBIND' in tcsh I believe but google this just to be safe.
-- Dale
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
