From owner-freebsd-bugs@FreeBSD.ORG  Sun Apr  1 20:20:09 2007
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
X-Original-To: freebsd-bugs@hub.freebsd.org
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 0262716A403
	for <freebsd-bugs@hub.freebsd.org>;
	Sun,  1 Apr 2007 20:20:09 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40])
	by mx1.freebsd.org (Postfix) with ESMTP id E67B813C4B9
	for <freebsd-bugs@hub.freebsd.org>;
	Sun,  1 Apr 2007 20:20:08 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l31KK8Wj079691
	for <freebsd-bugs@freefall.freebsd.org>; Sun, 1 Apr 2007 20:20:08 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l31KK8w8079690;
	Sun, 1 Apr 2007 20:20:08 GMT (envelope-from gnats)
Date: Sun, 1 Apr 2007 20:20:08 GMT
Message-Id: <200704012020.l31KK8w8079690@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: "R. B. Riddick" <arne_woerner@yahoo.com>
Cc: 
Subject: Re: bin/111101: /usr/bin/lockf: when lockf blocks due to another
	lockf and no -k is specified and the other lockf ends,
	the file is away
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "R. B. Riddick" <arne_woerner@yahoo.com>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Apr 2007 20:20:09 -0000

The following reply was made to PR bin/111101; it has been noted by GNATS.

From: "R. B. Riddick" <arne_woerner@yahoo.com>
To: Kris Kennaway <kris@obsecurity.org>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: bin/111101: /usr/bin/lockf: when lockf blocks due to another lockf and no -k is specified and the other lockf ends, the file is away
Date: Sun, 1 Apr 2007 13:11:04 -0700 (PDT)

 --- Kris Kennaway <kris@obsecurity.org> wrote:
 > > Explicitly? Documented? Since I have not found that documentation, can u
 > > help me a little bit by showing it?
 > > 
 > > In the mean time I show a piece of my documentation (man page lockf(1)):
 > > "DESCRIPTION
 > >      The lockf utility acquires an exclusive lock on a file, creating it if
 > >      necessary, and removing the file on exit unless explicitly told not
 > >      to.
 >                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 > 
 > This is even underlined.
 >
 Hmm... I was talking of the second lockf process, that does not create the
 file, but that holds an exclusive lock on an unlinked file, which is completely
 useless.
 
 > > If think, the explicit documentation says, that the file is created
 > > (although
 > > this "if necessary" is somewhat weaselish, so that the man page should be
 > > changed, too; it should say: "creating it if it does not exist").
 > 
 > But that is what "if necessary" means.
 >
 Water on my mills... There u have the contradiction...
 
 > If you would like to submit a manpage change to expand upon the
 > problems that can occur when not using -k, please go ahead.
 > 
 Hmm... As long as u say, that I dont understand the use of lockf(1), I will not
 say/request so much about it...
 
 :-)
 
 -Arne
 
 
  
 ____________________________________________________________________________________
 Don't pick lemons.
 See all the new 2007 cars at Yahoo! Autos.
 http://autos.yahoo.com/new_cars.html