From owner-freebsd-hackers Tue Oct 1 17:20:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA14442 for hackers-outgoing; Tue, 1 Oct 1996 17:20:37 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA14436 for ; Tue, 1 Oct 1996 17:20:34 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id AAA01323; Wed, 2 Oct 1996 00:20:25 GMT Date: Wed, 2 Oct 1996 09:20:25 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: julian@whistle.com, eng@alpo.whistle.com, hackers@freebsd.org Subject: Re: flock/sendmail stuffup In-Reply-To: <199610011800.LAA02000@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 1 Oct 1996, Terry Lambert wrote: > > On Mon, 30 Sep 1996, Terry Lambert wrote: > > > > > 8-). Already there. flock uses an advisory range lock on the entire > > > file -- that's how it operates: it's a simplified special case of fcntl() > > > locking. > > > > flock also has better semantics. I think fcntl() still releases all locks > > when any one process closes the file. > > I will have to check it. If it does, it is in error. Locks must be I think Posix also adopted it's bogosity, because too many vendors complained. Regards, Mike Hancock