From owner-freebsd-arch Wed Aug 1 12:11:31 2001 Delivered-To: freebsd-arch@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id B014C37B401; Wed, 1 Aug 2001 12:11:28 -0700 (PDT) Date: Wed, 1 Aug 2001 12:11:28 -0700 From: David O'Brien To: Robert Watson Cc: Nate Williams , arch@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disabling portmapper (was Re: Patch to modify default inetd.conf, have sysinstall prompt to edit , inetd.conf) Message-ID: <20010801121128.B10275@hub.freebsd.org> Reply-To: obrien@freebsd.org References: <15207.35178.61523.131897@nomad.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.ORG on Wed, Aug 01, 2001 at 09:08:29AM -0400 X-Operating-System: FreeBSD 4.3-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 01, 2001 at 09:08:29AM -0400, Robert Watson wrote: > I'd be tempted to disable the portmapper (rpcbind in -CURRENT) by default, > allowing it to either be manually enabled, or enabled by virtue of > dependencies (something we already support). It already is disabled in -current since 2000-07-28 22:45:36 portmap_enable="NO" # Run the portmapper service (YES/NO). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message