Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!sri-unix!hplabs!hpcea!hpda!hppcgo!hpisoa2!hpisod1!hpisoa1!davel
From: davel@hpisoa1.HP.COM (Dave Lennert)
Newsgroups: comp.unix.wizards
Subject: Re: Wanted: lockf system call source
Message-ID: <2200003@hpisoa1.HP.COM>
Date: Mon, 24-Nov-86 00:30:07 EST
Article-I.D.: hpisoa1.2200003
Posted: Mon Nov 24 00:30:07 1986
Date-Received: Wed, 26-Nov-86 20:48:13 EST
References: <110@dvm.UUCP>
Lines: 12

One interesting thing I noticed about implementing lockf() on top of SysV
fcntl() file locking is that (it appears) fcntl() requires that the file
be opened with write permission even for read locking.  Lockf() does not
require this.

I'm I correctly stating the situation?  If so, is this regarded as a 
deficiency in SysV's lockf()?

    Dave Lennert                ucbvax!hpda!davel               [UUCP]
    Hewlett-Packard - 47UX      ihnp4!hplabs!hpda!davel         [UUCP]
    19447 Pruneridge Ave.       
    Cupertino, CA  95014        (408) 447-6325                  [AT&T]