From owner-freebsd-current Mon May 5 14:33:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA21881 for current-outgoing; Mon, 5 May 1997 14:33:49 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA21874 for ; Mon, 5 May 1997 14:33:44 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA16759 for current@freebsd.org; Mon, 5 May 1997 14:31:10 -0700 From: Terry Lambert Message-Id: <199705052131.OAA16759@phaeton.artisoft.com> Subject: Bug: is it the kernel or the man page? To: current@freebsd.org Date: Mon, 5 May 1997 14:31:10 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, it looks like a bug in the close(2) man page. The man page does not indicate that the advisory record locks on a file are lost on the first close, even if you have multiple fd's for the same file. The kernel code (kern_descrip.c/closef) says that this is correct POSIX behaviour (though it really makes one wonder how the hell such a system could successfully support an NFS lockd, which wants to coelesce lock sets to a single descriptor so it can support a larger number of clients!). Could someone with commit priveledges fix the man page? Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.