From owner-freebsd-hackers@FreeBSD.ORG  Wed Jun 22 16:33:59 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 63A6A16A41F;
	Wed, 22 Jun 2005 16:33:59 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from harmony.village.org (unknown [199.45.160.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5DCA643D1F;
	Wed, 22 Jun 2005 16:33:57 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from localhost (localhost.village.org [127.0.0.1])
	by harmony.village.org (8.13.3/8.13.3) with ESMTP id j5MEpXX1053144;
	Wed, 22 Jun 2005 08:51:33 -0600 (MDT) (envelope-from imp@bsdimp.com)
Date: Wed, 22 Jun 2005 08:53:00 -0600 (MDT)
Message-Id: <20050622.085300.82192668.imp@bsdimp.com>
To: deischen@freebsd.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <Pine.GSO.4.43.0506221027490.22792-100000@sea.ntplx.net>
References: <34cb7c8405062207246b582eaf@mail.gmail.com>
	<Pine.GSO.4.43.0506221027490.22792-100000@sea.ntplx.net>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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
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: Wed, 22 Jun 2005 16:33:59 -0000

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.

Warner