Date: Mon, 24 Sep 2007 22:56:14 GMT From: csjp@FreeBSD.org To: bilbo@hobbiton.org, csjp@FreeBSD.org, freebsd-bugs@FreeBSD.org, csjp@FreeBSD.org Subject: Re: bin/114341: lockf(1) utility is severely broken Message-ID: <200709242256.l8OMuEqv011104@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
Synopsis: lockf(1) utility is severely broken State-Changed-From-To: open->analyzed State-Changed-By: csjp State-Changed-When: Mon Sep 24 22:51:39 UTC 2007 State-Changed-Why: I will take this PR. I made this change. Currently its behaving the way it should be. If you want to use lockf for mutual exclusion, then you must use -k. There is no way it can mutually exclude if you let lockf delete the lock object from visibility to other processes. This is also being tracked under another PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=116543 Responsible-Changed-From-To: freebsd-bugs->csjp Responsible-Changed-By: csjp Responsible-Changed-When: Mon Sep 24 22:51:39 UTC 2007 Responsible-Changed-Why: I will take this PR. I made this change. Currently its behaving the way it should be. If you want to use lockf for mutual exclusion, then you must use -k. There is no way it can mutually exclude if you let lockf delete the lock object from visibility to other processes. This is also being tracked under another PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=116543 http://www.freebsd.org/cgi/query-pr.cgi?pr=114341
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200709242256.l8OMuEqv011104>