Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.ultrix
Subject: Re: Bug in DECstation Ultrix 3.1 NFS locking?
Message-ID: <8095@cbmvax.UUCP>
Date: 5 Oct 89 01:35:48 GMT
References: <3196@rti.UUCP> <8076@cbmvax.UUCP> <9001@batcomputer.tn.cornell.edu>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Distribution: comp
Organization: Commodore Technology, West Chester, PA
Lines: 29

In article <9001@batcomputer.tn.cornell.edu> riley@tcgould.tn.cornell.edu (Daniel S. Riley) writes:
> In article <8076@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) writes:
> >In article <3196@rti.UUCP> trt@rti.UUCP (Thomas Truscott) writes:
> >> We have been trying like crazy to get "lockf" to work
> >> correctly under DECstation Ultrix3.1, to no avail.
> 
> >RESTRICTIONS
> >     File region locking is not supported over NFS.
vs.
> ...
>      File region locking is supported over NFS, if the NFS lock-
>      ing service has been enabled.
> 
> Seems a bit contradictory, doesn't it.  Have you used nfssetlock to enable
> NFS locking service?  (Apologies if this is too obvious--I'm still a novice
> at managing Ultrix systems.)

Oops, sorry.  I knew there was some reason I was going to run catman (pain)
after doing the 3.1 upgrade.  It appears that NFS locking arrived with 3.1.

It seems that you need both an appropriate complement of daemons and to
run this enable program.  I'd consult the man pages for lockf and all
what's crossreferenced thereto and perhaps the 3.0 -> 3.1 upgrade notes.
If you've attended to all these details and still have a problem...

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)