From owner-freebsd-threads@FreeBSD.ORG Tue Apr 5 18:12:09 2005 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 073AE16A4CE for ; Tue, 5 Apr 2005 18:12:09 +0000 (GMT) Received: from silver.he.iki.fi (helenius.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6437943D31 for ; Tue, 5 Apr 2005 18:12:07 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from [193.64.42.134] (h86.vuokselantie10.fi [193.64.42.134]) by silver.he.iki.fi (8.13.1/8.11.4) with ESMTP id j35IC5tJ034169; Tue, 5 Apr 2005 21:12:05 +0300 (EEST) (envelope-from pete@he.iki.fi) Message-ID: <4252D50C.3000007@he.iki.fi> Date: Tue, 05 Apr 2005 21:12:28 +0300 From: Petri Helenius User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sean Chittenden References: <20050405174828.GQ1527@sean.gigave.com> In-Reply-To: <20050405174828.GQ1527@sean.gigave.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: threads@freebsd.org Subject: Re: pthread_acquire() still having issues? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2005 18:12:09 -0000 That refers to the linuxthreads issue, right? It does not describe the alleged pthread issue to any great detail. Pete Sean Chittenden wrote: >I'd nearly call this Nagios FUD, but since I haven't seen anything >about this I thought I'd as for the record. From the Known Issues >section on: > >http://nagios.sourceforge.net/docs/2_0/whatsnew.html > >"There are a few known issues with the Nagios 2.0 code at the >moment. Hopefully some of these will be fixed before 2.0 is released >as stable... FreeBSD and threads. On FreeBSD there's a native >user-level implementation of threads called 'pthread' and there's also >an optional ports collection 'linuxthreads' that uses kernel >hooks. Some folks from Yahoo! have reported that using the pthread >library causes Nagios to pause under heavy I/O load, causing some >service check results to be lost. Switching to linuxthreads seems to >help this problem, but not fix it. The lock happens in liblthread's >__pthread_acquire() - it can't ever acquire the spinlock. It happens >when the main thread forks to execute an active check. On the second >fork to create the grandchild, the grandchild is created by fork, but >never returns from liblthread's fork wrapper, because it's stuck in >__pthread_acquire(). Maybe some FreeBSD users can help out with this >problem." > >I cruised through the lists and didn't see anything. Has this been >addressed or is this still a current issue that folks are aware of? >-sc > > >