From owner-freebsd-current  Thu Apr 17 05:43:19 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA29159
          for current-outgoing; Thu, 17 Apr 1997 05:43:19 -0700 (PDT)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA29149
          for <current@freebsd.org>; Thu, 17 Apr 1997 05:43:14 -0700 (PDT)
Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2])
	by nlsystems.com (8.8.5/8.8.5) with SMTP id NAA26799;
	Thu, 17 Apr 1997 13:42:55 +0100 (BST)
Date: Thu, 17 Apr 1997 13:42:55 +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.
In-Reply-To: <199704150152.UAA11924@sierra.zyzzyva.com>
Message-ID: <Pine.BSF.3.95q.970417134207.4123O-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

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