From owner-freebsd-hackers  Mon Sep 30 22:02:56 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id WAA27323
          for hackers-outgoing; Mon, 30 Sep 1996 22:02:56 -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 WAA27316
          for <hackers@freebsd.org>; Mon, 30 Sep 1996 22:02:52 -0700 (PDT)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id FAA23414; Tue, 1 Oct 1996 05:01:59 GMT
Date: Tue, 1 Oct 1996 14:01:58 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: Terry Lambert <terry@lambert.org>
cc: Julian Elischer <julian@whistle.com>, eng@alpo.whistle.com,
        hackers@freebsd.org
Subject: Re: flock/sendmail stuffup
In-Reply-To: <199609301816.LAA06288@phaeton.artisoft.com>
Message-ID: <Pine.SV4.3.93.961001135922.22919D-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

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.

Regards,


Mike Hancock