Path: utzoo!attcan!uunet!smsdpg!seg
From: seg@smsdpg.uu.net (Scott Garfinkle)
Newsgroups: comp.protocols.nfs
Subject: Re: PC-NFS Locking Problem
Message-ID: <186@smsdpg.uu.net>
Date: 25 Jan 89 14:19:04 GMT
References: <449@eagle_snax.UUCP>
Organization: SMS Data Products Group, Reston VA
Lines: 27

From article <449@eagle_snax.UUCP>, by geoff@eagle_snax.UUCP ( R.H. coast near the top):
> In article <183@smsdpg.uu.net> seg@smsdpg.uu.net (Scott Garfinkle) writes:
	/* The original article referred to trying to acquire a lock on a file
	 * via PC-NFS.  I still haven't figured out how.  Geoff replies:
	 */
> The use of SHARE is completrely irrelevant, although if you start it
> after PC-NFS it may confuse things (I'll try it in a few minutes).
True!  NFS redirector lets you apply locking() to NFS files, even if share
isn't loaded (good idea).

> The server must be running a version of the lock manager which supports
> the PC extensions....
Yes, our server does.  As I'd said, we're running SunOS4.0.  In fact, I'd even
tried using the (older) lockd supplied with PC-NFS to see if would help.

> ...if you prefer to run NET USE by hand, append a "/MS" switch to the command.
I've been using /sh.  When we use /ms (must share), applying a lock to a file
from one pc causes all other pcs to be locked out from all file accesses in
that net drive.  Even if the lock is applied to a file in a subdirectory,
another pc can't create files in a parent directory! Further, the
inaccessability from other nodes remains in effect even after the original
lock has been relinquished.

So, I'm not missing something obvious.  Is there somthing subtle?
		Scott E. Garfinkle
		SMS Data Products Group, Inc.
		uunet!smsdpg!seg