Date: Fri, 18 Apr 1997 19:50:03 -0500 From: Randy Terbush <randy@zyzzyva.com> To: Doug Rabson <dfr@nlsystems.com> Cc: Randy Terbush <randy@zyzzyva.com>, Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>, current@freebsd.org Subject: Re: (*my* problems found...yours?) NFS problems - it doesn't appear to be ep0. Message-ID: <199704190050.TAA22403@sierra.zyzzyva.com> In-Reply-To: dfr's message of Thu, 17 Apr 1997 13:42:55 %2B0100. <Pine.BSF.3.95q.970417134207.4123O-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Mon, 14 Apr 1997, Randy Terbush wrote: > > > > > Since 2.2-GAMMA a new flag has been added to the sysctl. > > By setting vfs.nfs.nfs_privport=0, NFS works fine. For some reason, > > the NFS server is booting with vfs.nfs.nfs_privport=1. Can anyone > > explain the use of this parameter? > > > > #> sysctl vfs > > vfs.nfs.nfs_privport: 0 > > vfs.nfs.async: 0 > > vfs.nfs.defect: 0 > > vfs.nfs.diskless_valid: 0 > > vfs.nfs.diskless_rootpath: > > vfs.nfs.diskless_swappath: > > This variable is set by mountd depending on whether or not you use the -n > option to mountd. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 951 1891 I have a 2.2.1 box trying to mount another 2.2.1 box. I get the following. In order to allow a mount, I need to change vfs.nfs.nfs_privport=0. I am running 'mountd' _without_ a -n flag. NFS request from unprivileged port (123.223.323.423:1314) NFS request from unprivileged port (123.223.323.423:1314) NFS request from unprivileged port (123.223.323.423:1314) NFS request from unprivileged port (123.223.323.423:1314) NFS request from unprivileged port (123.223.323.423:1314) NFS request from unprivileged port (123.223.323.423:1314)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704190050.TAA22403>