Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-unix!hplabs!hpcea!hpda!hpirs!hpisod1!hpisoa1!davel
From: davel@hpisoa1.HP.COM (Dave Lennert)
Newsgroups: comp.unix.wizards
Subject: Re: Wanted: lockf system call source
Message-ID: <2200006@hpisoa1.HP.COM>
Date: Wed, 3-Dec-86 11:34:12 EST
Article-I.D.: hpisoa1.2200006
Posted: Wed Dec  3 11:34:12 1986
Date-Received: Sat, 6-Dec-86 03:11:48 EST
References: <110@dvm.UUCP>
Lines: 16

Ooops...  What I meant to say was:

One interesting thing I noticed about implementing lockf() on top of SysV
fcntl() file locking is that (it appears) lockf() requires that the file
                                          ^^^^^
be opened with write permission even for read locking.  /usr/group 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]