From owner-freebsd-hackers Wed Apr 21 4:17:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gidgate.gid.co.uk (gidgate.gid.co.uk [193.123.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9A1E1153E2 for ; Wed, 21 Apr 1999 04:17:27 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.8.8/8.8.7) id MAA24937; Wed, 21 Apr 1999 12:14:20 +0100 (BST) (envelope-from rb) Message-Id: <3.0.6.32.19990421121220.007a9100@gid.co.uk> X-Sender: rbmail@gid.co.uk X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 21 Apr 1999 12:12:20 +0100 To: Graham Wheeler From: Bob Bishop Subject: Re: File locking problem Cc: hackers@FreeBSD.ORG In-Reply-To: <371D97C4.B7EFA0B1@cdsec.com> References: <199904201821.OAA16150@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 11:17 21/04/99 +0200, Graham Wheeler wrote: >[...] >So it seems that although my assorted processes are doing >things in the order: > > ... > child:unlink() > child:close() // and unlock > parent:open() // and lock - should not succeed due to unlink > parent:fgets() // should never occur as open() should fail > ... > >there is some kind of race happening between the file being removed >by the unlink and the parent:open() More than likely. unlink() has never claimed to be synchronous AFAIK. -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message