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

[R. B. Riddick]

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

From: "R. B. Riddick" <arne_woerner at yahoo.com>
To: Kris Kennaway <kris at obsecurity.org>
Cc: freebsd-gnats-submit at 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:18:44 -0700 (PDT)

 --- Kris Kennaway <kris at obsecurity.org> wrote:
 > On Sun, Apr 01, 2007 at 01:11:04PM -0700, R. B. Riddick wrote:
 > OK, if you dont want to pursue a documentation improvement then I'll
 > close the PR.
 > 
 Then I will continue to think, that lockf without -k is useless in many cases
 and very fünny/surprising/undöcumented.
 
 -Arne
 
 
  
 ____________________________________________________________________________________
 Expecting? Get great news right away with email Auto-Check. 
 Try the Yahoo! Mail Beta.
 http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html