Date: Sat, 19 Apr 1997 09:47:04 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Randy Terbush <randy@zyzzyva.com> Cc: 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: <Pine.BSF.3.95q.970419094309.428M-100000@herring.nlsystems.com> In-Reply-To: <199704190050.TAA22403@sierra.zyzzyva.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 18 Apr 1997, Randy Terbush wrote: > > 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. How are you mounting the directory? If you are using mount_nfs, it should be using privileged ports by default. If amd, then you either need to add 'resvport' to the mount options in the amd map or change the server to allow non-privileged ports (which you have done). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970419094309.428M-100000>