Date: Wed, 25 Jan 2012 17:54:59 -0500 From: Michael Butler <imb@protected-networks.net> To: Craig Rodrigues <rodrigc@crodrigues.org> Cc: Rick Macklem <rmacklem@uoguelph.ca>, freebsd-current@freebsd.org Subject: Re: Heads Up: NFS clients can now fail "mount -u -o udp..." Message-ID: <4F208843.5000100@protected-networks.net> In-Reply-To: <CAG=rPVeGRxM7USAbTeiyBYp0eduPA2MkHqBZH5pSmByr5hzFBQ@mail.gmail.com> References: <666472979.73336.1327451522107.JavaMail.root@erie.cs.uoguelph.ca> <CAG=rPVeGRxM7USAbTeiyBYp0eduPA2MkHqBZH5pSmByr5hzFBQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/25/12 17:44, Craig Rodrigues wrote: > If a user boots with an NFS root mount, and does not specify > UDP or TCP, what is the default transport protocol used? > > If I user does: "mount -t nfs ...." or "mount_nfs ...." > from the command-line, and does not specify UDP or TCP, what is the > default transport protocol used? > > I would like to see the default become TCP in both cases. > It would solve a lot of "FreeBSD out of the box" problems when interacting > with more modern NFS servers. The default is TCP, imb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8giEMACgkQQv9rrgRC1JLfTwCgp+5xi6/5tCoQpGER+TpR+LPK 2psAoMm7YVqCBdC/F/rGReWLMIXuNUBr =GVHN -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F208843.5000100>