From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 18:32:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAEFC16A402 for ; Mon, 10 Apr 2006 18:32:49 +0000 (UTC) (envelope-from rand@meridian-enviro.com) Received: from newman.meridian-enviro.com (newman.meridian-enviro.com [207.109.235.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B12D43D79 for ; Mon, 10 Apr 2006 18:32:42 +0000 (GMT) (envelope-from rand@meridian-enviro.com) X-Envelope-To: Received: from delta.meridian-enviro.com (delta.meridian-enviro.com [10.10.10.43]) by newman.meridian-enviro.com (8.13.1/8.13.1) with ESMTP id k3AIWfMZ079055 for ; Mon, 10 Apr 2006 13:32:41 -0500 (CDT) (envelope-from rand@meridian-enviro.com) Date: Mon, 10 Apr 2006 13:32:40 -0500 Message-ID: <87slol2sdz.wl%rand@meridian-enviro.com> From: "Douglas K. Rand" To: freebsd-hackers@freebsd.org User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: ClamAV 0.88/1389/Mon Apr 10 07:58:55 2006 on newman.meridian-enviro.com X-Virus-Status: Clean Subject: Nagios & Linux Threads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 18:32:49 -0000 I'm running Nagios 2.0 on FreeBSD 6 and I occasionally experience the problem originally discussed http://www.freebsd.org/cgi/getmsg.cgi?fetch=165398+171880+/usr/local/www/db/text/2005/freebsd-hackers/20050821.freebsd-hackers (That is: a forked nagios process that consumes as much CPU time as it can.) Living with this problem while annoying isn't the end of the world. I was looking for workarounds. One solution for a work around was to use Linux threads. I was wondering if anybody had managed to get Nagios 2.0 to use Linux threads successfully. And if so, what changes to the port were required.