On Tue, 18 Jun 2002 14:58:44 +0300 (IDT), Geoffrey S. Mendelson <[EMAIL PROTECTED]> wrote: > > Nathan Fain wrote: > > > > How can i test and verify that the lock manager is working and doing > > it's job over NFS? > > You can't. There is no NFS locking in kernels > 2.4.0 (and maybe > earlier). > > NFS locking used to work, but it never worked well, and the designers of it > could never come up with an ALL-INCLUSIVE locking system for NFS locks, so > they gave up.
As Ariel Biener <[EMAIL PROTECTED]> stated, NFS locking works on Linux (at least from kernel 2.2.x). The problem you are refering to is addressed by rpc.statd. From its man page: The rpc.statd server implements the NSM (Network Status Monitor) RPC protocol. This service is somewhat misnomed, since it doesn't actually provide active monitoring as one might suspect; instead, NSM implements a reboot notification service. It is used by the NFS file locking service, rpc.lockd, to implement lock recovery when the NFS server machine crashes and reboots. This also solves the lost connection problem - the client reclaims the locks it had before the connection was lost. The remaining problem (the client machine does not release a lock when the locking process ends) can not be solved and is the same as locking on local FS (except that connection to local disk almost never fails). >From my experience I can testify that NFS locking is working on Linux better than on DG/UX (a dying OS) and IRIX (still floating). Ehud. -- Ehud Karni Tel: +972-3-7966-561 /"\ Mivtach - Simon Fax: +972-3-7966-667 \ / ASCII Ribbon Campaign Insurance agencies (USA) voice mail and X Against HTML Mail http://www.mvs.co.il FAX: 1-815-5509341 / \ mailto:[EMAIL PROTECTED] Better Safe Than Sorry ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]