Date: Tue, 20 Feb 2007 23:39:22 +0100 (CET) From: Martin Blapp <mb@imp.ch> To: Daniel Eischen <deischen@freebsd.org> Cc: rob@debank.tv, freebsd-threads@freebsd.org Subject: Re: 6.2-Release and Clamd 0.90 with libpthread.so Message-ID: <20070220233322.M4139@godot.imp.ch> In-Reply-To: <Pine.GSO.4.64.0702201724590.12034@sea.ntplx.net> References: <20070220153632.E4139@godot.imp.ch> <Pine.GSO.4.64.0702201138080.12034@sea.ntplx.net> <20070220174221.B4139@godot.imp.ch> <Pine.GSO.4.64.0702201145420.12034@sea.ntplx.net> <20070220190347.C4139@godot.imp.ch> <Pine.GSO.4.64.0702201319230.12034@sea.ntplx.net> <20070220225303.V4139@godot.imp.ch> <Pine.GSO.4.64.0702201724590.12034@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > If running in foreground works regardless of kern.threads.virtual_cpu > (there will still be some inefficiencies here because of the > scheduler and KSE overhead/contention), then it is probably due > to the application doing a fork() from a threaded application > without doing an exec(). This is prohibited by POSIX and > libpthread makes no attempt to allow it. Yes it works regardless of kern.threads.virtual_cpu. Yes, fork() is called without exec(). So what's the proper way ? Start clamd in foreground mode with daemon /usr/local/sbin/clamd And redirect stderr ? Or can this be solved differently ? Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070220233322.M4139>