Date: Sat, 6 Nov 1999 13:29:16 -0600 (CST) From: Jonathan Lemon <jlemon@americantv.com> To: dwmalone@maths.tcd.ie, current@freebsd.org, Ollivier Robert <roberto@keltia.freenix.fr> Subject: Re: Serious locking problem in CURRENT Message-ID: <199911061929.NAA26145@free.pcs> In-Reply-To: <local.mail.freebsd-current/19991106134548.A2921@walton.maths.tcd.ie> References: <local.mail.freebsd-current/19991105225916.A14961@keltia.freenix.fr> <local.mail.freebsd-current/19991106005016.A865@keltia.freenix.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <local.mail.freebsd-current/19991106134548.A2921@walton.maths.tcd.ie> 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 majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911061929.NAA26145>