From owner-freebsd-current  Sun Nov  7  3:51:16 1999
Delivered-To: freebsd-current@freebsd.org
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by hub.freebsd.org (Postfix) with SMTP id 9DA2514C02
	for <current@freebsd.org>; Sun,  7 Nov 1999 03:51:10 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa35858@salmon>; 7 Nov 1999 11:51:09 +0000 (GMT)
Date: Sun, 7 Nov 1999 11:51:06 +0000
From: David Malone <dwmalone@maths.tcd.ie>
To: Ollivier Robert <roberto@keltia.freenix.fr>
Cc: current@freebsd.org
Subject: Re: Serious locking problem in CURRENT
Message-ID: <19991107115106.A15177@walton.maths.tcd.ie>
References: <local.mail.freebsd-current/19991105225916.A14961@keltia.freenix.fr> <local.mail.freebsd-current/19991106005016.A865@keltia.freenix.fr> <local.mail.freebsd-current/19991106134548.A2921@walton.maths.tcd.ie> <199911061929.NAA26145@free.pcs> <19991107020102.A9992@keltia.freenix.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <19991107020102.A9992@keltia.freenix.fr>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Nov 07, 1999 at 02:01:02AM +0100, Ollivier Robert wrote:

> Right but in Postfix case this is not the case. The "master" process run to
> check whether Postfix is running or not is definitely NOT a child of the real
> "master" process.

But if the real master process forks and then it's child closes the fd
which the lock was on, then the master process will have lost it's lock.
Is this likely? Does the real master fork children to do stuff?

	David.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message