From owner-freebsd-hackers Wed Aug 25 3: 8:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 59A78152EF for ; Wed, 25 Aug 1999 03:08:43 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id GAA01282; Wed, 25 Aug 1999 06:05:14 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id GAA23574; Wed, 25 Aug 1999 06:05:13 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id GAA95394; Wed, 25 Aug 1999 06:05:11 -0400 (EDT) Date: Wed, 25 Aug 1999 06:05:11 -0400 (EDT) From: Thomas David Rivers Message-Id: <199908251005.GAA95394@lakes.dignus.com> To: bee@wipinfo.soft.net, hackers@FreeBSD.ORG Subject: RE: Mandatory locking? In-Reply-To: <000301beeea6$1ea898a0$88291fac@wipro.tcpn.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > All the files under Tandem's NSK has mandatory locking. The file cannot be > opened if another process has it opened. some thing like > > * if the file is opened for reading, any one can open it for > reading but opening for writing gives error > * if the file is open for writing, it can't be opened for > read/write > * if the process holding the file is killed, the lock is gone > * it is possible to get the pid of the process(es) which has > a given file open (like which process has file "xyz" open? > kind of query). btw, is there any way to get this info now in FBSD? This sounds interesting... But - aren't there NFS issues? I mean, in stateless access to a file - how do you know if the process holding the file is killed if it's remote? Just curious... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message