proposed lock driver

[utzoo!decvax!ucbvax!unix-wizards]

>From mo at LBL-UNIX Wed Aug 19 12:39:01 1981
The lock driver proposed in the code fragment  may have problems with
the Unix "feature" of not calling close until possibly after you close it.
Other schemes like this have added a "lock-breaking" call in the kernel
exit() code to insure locks get broken.  This means also having to keep
track of the lock owner if more than one lock is held.  Does the
proffered code have this problem?
	-Mike