Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 (Tek) 9/28/84 based on 9/17/84; site lumiere.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tektronix!lumiere!richl
From: richl@lumiere.UUCP (Rick Lindsley)
Newsgroups: net.bugs.4bsd
Subject: Re: EXCL without CREAT
Message-ID: <1574@lumiere.UUCP>
Date: Wed, 8-Jan-86 13:33:58 EST
Article-I.D.: lumiere.1574
Posted: Wed Jan  8 13:33:58 1986
Date-Received: Sat, 11-Jan-86 07:32:04 EST
References: <5507@allegra.UUCP> <6220@utzoo.UUCP> <7022@ki4pv.UUCP>
Reply-To: richl@lumiere.UUCP (Rick Lindsley)
Organization: Tektronix, Beaverton OR
Lines: 14
Summary: 

In article <7022@ki4pv.UUCP> tanner@ki4pv.UUCP (Tanner Andrews) writes:

>Security is easily solved by refusing to allow locking a file unless
>the file has been successfully opened for WRITE -- there's no real
>excuse for a read-only prog to need to lock a file if the write-file
>prog successfully locks the damned thing anyway.

Not true -- I may be doing a series of non-atomic reads, and I don't want
things changing under me by another program writing in between my reads.
That is where the shared lock comes in handy -- no need to disallow others
from reading too, but if you want to write, you should get exclusive
access.

Rick Lindsley