🚀 go-pugleaf

I ran into a very frustrating problem today with lockf().  I have two
programs, call thme big and small.  Small is a test program designed
to open() a file and then lockf() it.  Big [hacked version of bibcard]
is an xview program that does the same thing at one point.  Here's the
weirdness:

a>
run small  [locks file]
run small  [reports file locked, correct behavior]

b>
run small  [locks file]
run big    [reports file locked, correct behavior]

c>
run big    [locks file???]
run small  [does not report file locked!, Incorrect behavior.]

d>
run big    [locks file???]
run small  [does not report file locked!, Incorrect behavior.]
run small  [reprts file locked, but probably due to small.]

The locking code is identical in the two programs (i.e., emacs
cut-and-paste.)  Any ideas/suggestions are sought!  Please respond by
email.  Thanx for your help.

--
Gerry Roston (gerry@cs.cmu.edu) | Why has government been instituted at all?
Field Robotics Center,          | Because the passions of man will not con-
Carnegie Mellon University      | form to the dictates of reason and justice
Pittsburgh, PA, 15213           | without constraint.  Alexander Hamilton
(412) 268-3856                  | 
                                | 
The opinions expressed are mine | 
and do not reflect the official | 
position of CMU, FRC, RedZone,  | 
or any other organization.      |