Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!lll-tis!ptsfa!ihnp4!islenet!richard
From: richard@islenet.UUCP
Newsgroups: comp.sys.att,unix-pc.general
Subject: lockf on the 7300
Message-ID: <3429@islenet.UUCP>
Date: Sat, 15-Aug-87 14:37:38 EDT
Article-I.D.: islenet.3429
Posted: Sat Aug 15 14:37:38 1987
Date-Received: Sun, 16-Aug-87 22:08:43 EDT
Organization: Islenet Inc.,  Honolulu
Lines: 18
Xref: utgpu comp.sys.att:827 junk:5613

I noticed that there is no entry in /lib/shlib.ifile for lockf(3),
though I did find a reference to "locking".

Hoping to use the shared library with a program I'm working on I used
ar to extract the lockf.o module from /lib/libc.a and linked that
in with my stuff and the shared libraries.  But although the non-shared
version seems to work just fine, with shlib it gets locked up occasionally.

Is there some reason why file locking won't work with a program
linked with the shared library?

That "locking" entry in shlib.ifile looks a bit strange, reminiscent
of a call by that name in old V7 Unisoft unix.

Richard
-- 
Richard Foulk		...{dual,vortex,ihnp4}!islenet!richard
Honolulu, Hawaii