From owner-freebsd-fs@FreeBSD.ORG  Sun Nov 14 17:10:24 2010
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3FA7A1065674
	for <freebsd-fs@freebsd.org>; Sun, 14 Nov 2010 17:10:24 +0000 (UTC)
	(envelope-from v.velox@vvelox.net)
Received: from vulpes.vvelox.net (sula-ki.vvelox.net [99.69.115.46])
	by mx1.freebsd.org (Postfix) with ESMTP id E9A7F8FC13
	for <freebsd-fs@freebsd.org>; Sun, 14 Nov 2010 17:10:23 +0000 (UTC)
Received: from vixen42.vulpes.vvelox.net (unknown [192.168.14.2])
	(Authenticated sender: v.velox)
	by vulpes.vvelox.net (Postfix) with ESMTPA id 2D53AB882;
	Sun, 14 Nov 2010 10:17:37 -0600 (CST)
Date: Sun, 14 Nov 2010 10:13:24 -0600
From: "Zane C.B." <v.velox@vvelox.net>
To: Jeremy Chadwick <freebsd@jdc.parodius.com>
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>
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; amd64-portbld-freebsd8.1)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1;
	boundary="Sig_/daoOeefSdA5ViHWzjJh3PRH";
	protocol="application/pgp-signature"
Cc: freebsd-fs@freebsd.org
Subject: Re: NFS locking
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Nov 2010 17:10:24 -0000

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