Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: lockf() without fcntl interface?
Message-ID: <5696@brl-smoke.ARPA>
Date: Fri, 20-Mar-87 16:57:08 EST
Article-I.D.: brl-smok.5696
Posted: Fri Mar 20 16:57:08 1987
Date-Received: Wed, 25-Mar-87 03:39:50 EST
References: <43167@beno.seismo.CSS.GOV>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 10

In article <43167@beno.seismo.CSS.GOV> rick@seismo.CSS.GOV (Rick Adams) writes:
>Are there any unix implementations that offer a SVID lockf() compatible
>file locking that do NOT also support the same locking via fcntl()?

The general answer is, yes.  lockf() was specified in the 1984
/usr/group Standard, and was derived from John Bass's implementation
found in some pre-System V UNIX or UNIX-like systems.  fcntl()
locking appeared slightly after SVR2.0.  Unfortunately IEEE 1003.1
has not yet to my knowledge replaced lockf() with the fcntl()
approach (which I find much superior).