On Tue, 09 Nov 2004 10:34:53 +0700 "Fajar A. Nugraha" <[EMAIL PROTECTED]> wrote:
> Tue Nov 9 10:28:54 2004 -> > /var/spool/exim/scan/1CRMgW-0004yX-Mv/1CRMgW-0004yX-Mv.eml: > Worm.Bagle.AU FOUND > Tue Nov 9 10:28:55 2004 -> ERROR: pthread_create failed > Tue Nov 9 10:28:55 2004 -> ERROR: pthread_create failed > Tue Nov 9 10:28:55 2004 -> ERROR: pthread_create failed > Tue Nov 9 10:28:55 2004 -> ERROR: pthread_create failed > Tue Nov 9 10:28:55 2004 -> ERROR: pthread_create failed > Tue Nov 9 10:28:55 2004 -> ERROR: pthread_create failed > Tue Nov 9 10:28:55 2004 -> ERROR: pthread_create failed > Tue Nov 9 10:28:56 2004 -> ERROR: pthread_create failed > Tue Nov 9 10:28:56 2004 -> ERROR: pthread_create failed At the moment, ExitOnOOM only reacts on memory allocation errors reported by libclamav. I will extend it to local cases later today. > I suspect this is also memory related since if I increase ulimits to Yes, it is. > On the side note, if the error is "calloc_problem: Cannot allocate > memory", I see clamd now gracefuly dies and daemontools kick in > immediately. Which is good. I didn't test ExitOnOOM, so thanks for the info :-) > Now, shouldn't the same behaviour also happen on pthread errors? Yes, it should. -- oo ..... Tomasz Kojm <[EMAIL PROTECTED]> (\/)\......... http://www.ClamAV.net/gpg/tkojm.gpg \..........._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Tue Nov 9 07:34:34 CET 2004
pgpaQUCGpD8rp.pgp
Description: PGP signature
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
