Any time I start lockd on the server, I get the message below in
dmesg.
NLM: failed to contact remote rpcbind, stat = 0, port = 0
NLM: failed to contact remote rpcbind, stat = 0, port = 0
Can't start NLM - unable to contact NSM
Any ideas?
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2010-03/msg00484.html
Solution (for me):
http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/056043.html
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
_______________________________________________
freeb...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-...@freebsd.org"
> On Tue, Nov 09, 2010 at 10:17:40AM -0600, Zane C.B. wrote:
> > What does it take to get NFS locking working?
> >
> > Any time I start lockd on the server, I get the message below in
> > dmesg.
> >
> > NLM: failed to contact remote rpcbind, stat = 0, port = 0
> > NLM: failed to contact remote rpcbind, stat = 0, port = 0
> > Can't start NLM - unable to contact NSM
> >
> > Any ideas?
>
> http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2010-03/msg00484.html
>
> Solution (for me):
>
> http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/056043.html
Ahh! Thanks.
Got poking through those two and noticed what I missed. rpc.lockd
requires rpc.statd.