From owner-freebsd-hackers@FreeBSD.ORG  Thu Jun 23 01:48:29 2005
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: 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 7147416A41C
	for <hackers@freebsd.org>; Thu, 23 Jun 2005 01:48:29 +0000 (GMT)
	(envelope-from deischen@freebsd.org)
Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1EC6443D55
	for <hackers@freebsd.org>; Thu, 23 Jun 2005 01:48:29 +0000 (GMT)
	(envelope-from deischen@freebsd.org)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
	by mail.ntplx.net (8.13.4/8.13.4/NETPLEX) with ESMTP id j5N1mDUb007642; 
	Wed, 22 Jun 2005 21:48:13 -0400 (EDT)
Date: Wed, 22 Jun 2005 21:48:13 -0400 (EDT)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
To: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20050622.085300.82192668.imp@bsdimp.com>
Message-ID: <Pine.GSO.4.43.0506222146570.25618-100000@sea.ntplx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net)
Cc: spork@fasttrackmonkey.com, hackers@freebsd.org, kamalp@acm.org,
	peadar.edwards@gmail.com
Subject: Re: Nagios and threads
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Daniel Eischen <deischen@freebsd.org>
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2005 01:48:29 -0000

On Wed, 22 Jun 2005, M. Warner Losh wrote:

> In message: <Pine.GSO.4.43.0506221027490.22792-100000@sea.ntplx.net>
>             Daniel Eischen <deischen@freebsd.org> writes:
> : We do protect the malloc lock across a fork(), but that's it.
>
> With 4.x libc_r, you could easily get hangs accross a fork() if you
> did anything before the exec (like setup fd's for stdin/out).  This
> was due to internal libc_r state being inconsistant.

I was only referring to libpthread in the above...  I don't think
libc_r is as robust in that regard.

-- 
DE