Date: Sun, 14 Nov 2010 10:13:24 -0600 From: "Zane C.B." <v.velox@vvelox.net> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-fs@freebsd.org Subject: Re: NFS locking Message-ID: <20101114101324.154a822e@vixen42.vulpes.vvelox.net> In-Reply-To: <20101109170104.GA37882@icarus.home.lan> References: <20101109101740.2e8e80ce@vixen42.vulpes.vvelox.net> <20101109170104.GA37882@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/daoOeefSdA5ViHWzjJh3PRH Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 9 Nov 2010 09:01:04 -0800 Jeremy Chadwick <freebsd@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? > >=20 > > Any time I start lockd on the server, I get the message below in > > dmesg. > >=20 > > NLM: failed to contact remote rpcbind, stat =3D 0, port =3D 0 > > NLM: failed to contact remote rpcbind, stat =3D 0, port =3D 0 > > Can't start NLM - unable to contact NSM > >=20 > > Any ideas? >=20 > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2010-03/msg00484.h= tml >=20 > Solution (for me): >=20 > 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. --Sig_/daoOeefSdA5ViHWzjJh3PRH Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkzgCq0ACgkQqrJJy0yxYQCFoQCfS9vic4zG7mMRbJMa4K2nvv1Q dvEAn1icpOlCuYmPc5GCCS3ff+chJNnQ =pbe7 -----END PGP SIGNATURE----- --Sig_/daoOeefSdA5ViHWzjJh3PRH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101114101324.154a822e>