Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: notesfiles
Path: utzoo!linus!decvax!wivax!cadmus!harvard!seismo!cmcl2!acf4!greenber
From: greenber@acf4.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Question on how to implement exclusi
Message-ID: <12200006@acf4.UUCP>
Date: Wed, 17-Oct-84 11:05:00 EST
Article-I.D.: acf4.12200006
Posted: Wed Oct 17 11:05:00 1984
Date-Received: Fri, 2-Nov-84 03:43:51 EST
References: <620@trwspp.UUCP>
Organization: New York University
Lines: 12
Nf-ID: #R:trwspp:-62000:acf4:12200006:000:463
Nf-From: acf4!greenber    Oct 17 09:05:00 1984

<>

In all of the routines that I've used, the kernel call for locking a file
require you to have "adequate" privledge.  In order to lock a file on read,
you must be owner or have write permission.  Otherwise, the lock call either
fails, or times out after about 2 "big" ticks..

It seems to work like a charm, and we haven't had any problem with it
(though I'm keeping my fingers crossed!)


Ross M. Greenberg  @ NYU   ---->  allegra!cmcl2!acf4!greenber  <----