Re: Serious locking problem in CURRENT

[Jonathan Lemon]

In article <local.mail.freebsd-current/[EMAIL PROTECTED]> you 
write:
>
>On Sat, Nov 06, 1999 at 12:50:16AM +0100, Ollivier Robert wrote:
>
>A child process seems to be able to let go of a parent's lock on
>4.0 by closing a file discriptor, the same doesn't seem to be true
>on 3.3.

>From the manual page for flock:

NOTES
     Locks are on files, not file descriptors.  That is, file descriptors du-
     plicated through dup(2) or fork(2) do not result in multiple instances of
     a lock, but rather multiple references to a single lock.  If a process
     holding a lock on a file forks and the child explicitly unlocks the file,
     the parent will lose its lock.

--
Jonathan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message