From owner-freebsd-current Tue Apr 8 16:34:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA10867 for current-outgoing; Tue, 8 Apr 1997 16:34:22 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA10859 for ; Tue, 8 Apr 1997 16:34:19 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id QAA09341; Tue, 8 Apr 1997 16:34:16 -0700 (PDT) Message-Id: <199704082334.QAA09341@austin.polstra.com> To: bemfica@militzer.me.tuns.ca Subject: Re: nfs problem Newsgroups: polstra.freebsd.current In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Tue, 08 Apr 1997 16:34:15 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , Antonio Bemfica wrote: > On Tue, 8 Apr 1997, Doug Rabson wrote: > > > FreeBSD-current now uses secure ports by default. > > And what would be the proper way to reconcile this new behaviour with the > requests by clients that want access through insecure ports? I'm having > problems with amd, and would not like to just "make it work" now when > there is a recommended way of doing it (especially if it will get "broken" > again the next time I recompile the system). You can either configure the clients to use reserved ports, or you can configure the server so that it doesn't require them. To make a client use reserved ports, just add the "resvport" option to its mount command lines, or to your amd map file: /defaults type:=host;fs:=${autodir}/${rhost};rhost:=${key} * opts:=rw,grpid,resvport This option has already been added to /usr/src/etc/amd.map, by the way. Somebody else on this list recently described how to change the server configuration. Sorry, I don't remember how. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth