Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

NFS locking

52 views
Skip to first unread message

Zane C.B.

unread,
Nov 9, 2010, 11:17:40 AM11/9/10
to
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?

signature.asc

Jeremy Chadwick

unread,
Nov 9, 2010, 12:01:04 PM11/9/10
to

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"

Zane C.B.

unread,
Nov 14, 2010, 11:13:24 AM11/14/10
to
On Tue, 9 Nov 2010 09:01:04 -0800
Jeremy Chadwick <fre...@jdc.parodius.com> wrote:

> 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.

signature.asc
0 new messages