Inaccuracy or even a Bug in Chapter "25.3.3 Locking" of the Free
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig1D5F4E900A8C223AD9FC834A
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
To whom it may concern,
I think I might have found an inaccuracy or maybe a bug in the
documentation concerning nfs: In Chapter "25.3.3 Locking" on the page
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-nfs.htm=
l
it says, that you need rpc.statd and rpc.lockd - but it doesn't say that
you need rpcbind to run these two. Of course rpcbind is mentioned on the
page, but only as needed for the nfs-server, not for the client.
(I found that solution on pipermail:
http://lists.freebsd.org/pipermail/freebsd-questions/2004-December/069022=
=2Ehtml
)
Maybe you want to update the Documentation to prevent Users from failing
in this point.
bye
Christian
--=20
Christian Marg mail: mailto:marg@rz.tu-clausthal.de
Rechenzentrum TU Clausthal web : http://www.rz.tu-clausthal.de
D-38678 Clausthal-Zellerfeld fon : 05323/72-2043
Germany ICQ : <on request>
--------------enig1D5F4E900A8C223AD9FC834A
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF2snBXwu7mUb3ymMRAiEwAJ9rPgoe5izzCKSptgnpeevnRgxP6gCfe3gv
PzxanUs0Gl2pzN2Jk3Z6Ww8=
=L2gO
-----END PGP SIGNATURE-----
--------------enig1D5F4E900A8C223AD9FC834A--