Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!uunet!mcsun!ukc!stl!siesoft!silver.siesoft.co.uk!andrew
From: andrew@siesoft.co.uk (Andrew Sinclair)
Newsgroups: comp.protocols.nfs
Subject: Locking Violation Problem
Summary: Why remount after a PC lock violation ?
Keywords: PC-NFS, Lock, Lock Manager, Mandatory, /MS
Message-ID: <1990Aug24.090955.28756@siesoft.co.uk>
Date: 24 Aug 90 09:09:55 GMT
Sender: andrew@siesoft.co.uk
Organization: Siemens System Developement Group, Bracknell, UK.
Lines: 23

In the PCNFS users guide under the section "locking files" it says :
If you invoke locking services with /MS ..... any DOS system call affecting the drive will cause a fatal error :

Locking violation
Abort, Retry or Ignore:

It then says that to recover you must unmount and remount the drive. Why ? 
Shouldn't it allow access once the lock has been removed (by the 
application/client that locked in the first place). Does this suggest that the 
client that gets in first and locks the file does not unlock it when it
has finished ? 

sounds like an odd spec of the lock manager to me ! Is there a way out of this ?
I do not want to remount my drives every time I see a locked file (I'll wait). 
What if I have other files open on that drive that I don't want to close ?

Thanx in advance
Andrew S.
--
+---------------------+----------------------------------------------------+
|Andrew Sinclair      |andrew.......                                       |   
|Siemens SDG          |                                                    |   
|Nixdorf House        |                                                    |