Date: Sun, 7 Nov 1999 02:01:02 +0100 From: Ollivier Robert <roberto@keltia.freenix.fr> To: current@freebsd.org Subject: Re: Serious locking problem in CURRENT Message-ID: <19991107020102.A9992@keltia.freenix.fr> In-Reply-To: <199911061929.NAA26145@free.pcs> References: <local.mail.freebsd-current/19991105225916.A14961@keltia.freenix.fr> <local.mail.freebsd-current/19991106005016.A865@keltia.freenix.fr> <local.mail.freebsd-current/19991106134548.A2921@walton.maths.tcd.ie> <199911061929.NAA26145@free.pcs>
next in thread | previous in thread | raw e-mail | index | archive | help
According to Jonathan Lemon: > 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. Right but in Postfix case this is not the case. The "master" process run to check whether Postfix is running or not is definitely NOT a child of the real "master" process. We just have a case where a lock on a given file is not seen at all by another process, thus defeating the whole idea. Locking is broken. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 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?19991107020102.A9992>