Date: Mon, 5 Mar 2007 01:02:06 +0100 (CET) From: Martin Blapp <mb@imp.ch> To: Daniel Eischen <deischen@freebsd.org> Cc: ClamAV Development <clamav-devel@lists.clamav.net>, freebsd-stable@freebsd.org Subject: Re: Clamav-90_2 Lockup with freebsd 6.2 Message-ID: <20070305005855.X18301@godot.imp.ch> In-Reply-To: <Pine.GSO.4.64.0703041838100.24018@sea.ntplx.net> References: <003701c75a03$fb478ac0$d801a8c0@dimuthu> <200702270305.l1R35MX2067221@lava.sentex.ca> <20070227035603.GA49430@tmn.ru> <20070227183553.B18301@godot.imp.ch> <20070304214255.O18301@godot.imp.ch> <Pine.GSO.4.64.0703041838100.24018@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > Make sure clamd is checking the return value of pthread_create() > for errors. You can also set LIBPTHREAD_PROCESS_SCOPE=yes or > LIBPTHREAD_SYSTEM_SCOPE=yes in your environment to force process > scope or system scope threads (libpthread only) for clamd. Yes, it does check the return value. And setting system or process scope doesn't make any difference. As I said, increasing the thread count works, decreading doesn't. -- Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070305005855.X18301>