On Tue, 23 Aug 2005 15:28:12 +0200
Manuel Bouyer <bouyer@antioche.eu.org> wrote:

> On Tue, Aug 23, 2005 at 03:18:59PM +0300, Mike M. Volokhov wrote:
> > On Mon, 22 Aug 2005 19:36:34 +0200
> > Manuel Bouyer <bouyer@antioche.eu.org> wrote:
> > 
> > > On Mon, Aug 22, 2005 at 03:09:28PM +0200, David Wetzel wrote:
> > > > hi,
> > > > 
> > > > I am using NFS between a NetBSD machine an Apple Tiger (latest version)
> > > > 
> > > > I keep getting messages like that on the mac:
> > > > 
> > > > nfs server myserver.example.com:/: lockd not responding
> > > > 
> > > > 
> > > > myserver# rpc.lockd -d 5
> > > > rpc.lockd: cannot get udp netconf.
> > > 
> > > Make sure you also have rpc.statd and rpcbind running.
> > 
> > Is it possible to solve/workaround this way (i.e. using lockd/statd)
> > old annoying "nfsrcvlk" trouble (please see kern/5960, kern/26209,
> > kern/29528, kern/30401 for examples)?
> 
> No, it's a completely different issue. lockd/statd is a protocol to allow
> NFS clients to lock files (using flock() or fnctl). It has nothing to do with
> nfsrcvlk which is an internal lock to the NFS code.

Aha, I see now (I'm not NFS expert). Thanks for the explaination!

> > 
> > Or it has been already fixed?
> 
> Some of these PRs may be fixed. 

Fixed or closed? Any chances to get nfsrcvlk hangs off?

--
Mishka.