From owner-freebsd-current Sun Nov 7 10: 5:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 15BAD14E52 for ; Sun, 7 Nov 1999 10:05:25 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id TAA28474 for current@freebsd.org; Sun, 7 Nov 1999 19:05:18 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id E5AE68711; Sun, 7 Nov 1999 16:37:18 +0100 (CET) Date: Sun, 7 Nov 1999 16:37:18 +0100 From: Ollivier Robert To: current@freebsd.org Subject: Re: Serious locking problem in CURRENT Message-ID: <19991107163718.A15753@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <199911061929.NAA26145@free.pcs> <19991107020102.A9992@keltia.freenix.fr> <19991107115106.A15177@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991107115106.A15177@walton.maths.tcd.ie> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to David Malone: > 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? All the time. "master" is an inetd-like daemon which spawn children according to master.cf. Everything run by Postfix is a child of "master"... I see your point and that's likely what happen. You're confirming what I thought about locking brokeness. That's bad. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message