On Thu, 2004-11-11 at 19:19, Bernhard Erdmann wrote:
Hi,
I'm running clamav 0.80 on SuSE Linux 9.0 / Exim 4.43 / exiscan / sa-exim.
15 times a day clamd segfaults but continues to run:
What exact version of zlib do you have installed? Upgrade to zlib 1.2.2.
Attach gdb to the clamd
I'm using a pop3 filtering box (with p3scan + clamav). I've updated
clamav from 0.75.1 to 0.80 and now on all the emails, clamdscan returns
code is 127, whereas p3scan was waiting for 0 or 1.
Anyone has an idea?
DamDam
___
After last message (clamd.log)
Fri Nov 12 13:02:53 2004 - Self checking every 1800 seconds.
Fri Nov 12 13:36:52 2004 - No stats for Database check - forcing reload
I gets 100% CPU load in top:
6828 clamav25 0 19280 5300 4012 R 89.1 3.3 0:50.78 clamd
Where I wrong?
clamav from cvs on
I'd like to log remoteIP when rejecting viruses, so that I can respond
quickly to local infections.
With other milters, I've stored the remote IP address into the privdata
structure. With clamav-milter, though, substantial restructuring seems to
be required, since remoteIP is only seen in the
On Thursday 11 November 2004 05:56 pm, Stephen Gran wrote:
[snip]
So, when start-stop-daemon (or daemon) sends a kill signal, it ends up
signalling the wrong thread, and it takes a long time for the signal to
work.
http://cr.yp.to/daemontools.html
http://smarden.org/runit
makes it very easy
Jon Dossey wrote:
able to offer some insight as to possible causes.
Which version of make are you using, BTW?
Look! Im *not* top posting this time! :)
Make version looks like 3.79.1
[EMAIL PROTECTED] root]# make --version
GNU Make version 3.79.1, by Richard Stallman and
On Fri, Nov 12, 2004 at 10:29:20AM -0600, Jeremy Kitchen said:
On Thursday 11 November 2004 05:56 pm, Stephen Gran wrote:
[snip]
So, when start-stop-daemon (or daemon) sends a kill signal, it ends up
signalling the wrong thread, and it takes a long time for the signal to
work.
