From owner-freebsd-stable@FreeBSD.ORG Tue Oct 17 15:26:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F5CF16A415 for ; Tue, 17 Oct 2006 15:26:03 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail.secureworks.net (mail.secureworks.net [65.114.32.155]) by mx1.FreeBSD.org (Postfix) with SMTP id 3996843D8F for ; Tue, 17 Oct 2006 15:25:50 +0000 (GMT) (envelope-from mike@jellydonut.org) Received: (qmail 54616 invoked from network); 17 Oct 2006 15:25:49 -0000 Received: from unknown (HELO ?192.168.23.35?) (63.239.86.252) by 0 with SMTP; 17 Oct 2006 15:25:49 -0000 Message-ID: <4534F5FE.30609@jellydonut.org> Date: Tue, 17 Oct 2006 11:25:50 -0400 From: Michael Proto User-Agent: Thunderbird 1.5.0.7 (X11/20060914) MIME-Version: 1.0 To: Brooks Davis References: <20061017082319.I27675@ramstind.fig.ol.no> <20061017143947.GA68977@lor.one-eyed-alien.net> <4534EC94.4090103@jellydonut.org> In-Reply-To: <4534EC94.4090103@jellydonut.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD stable Subject: Re: Ensuring inetd is started before any RPC services X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2006 15:26:03 -0000 Michael Proto wrote: > Brooks Davis wrote: >> On Tue, Oct 17, 2006 at 08:46:49AM +0200, Trond Endrest?l wrote: >>> I have on many occasions run into the situation where the RPC based >>> services have occupied the well-known ports for other non-RPC based >>> services. Last week rpc.lockd on one of my systems got hold of TCP >>> port 995, leaving inetd unable to start any pop3s services. >>> >>> The easy cure is to add this line >>> >>> # BEFORE: rpcbind >>> >>> to /etc/rc.d/inetd. >>> >>> You might want to consider fixing /etc/rc.d/inetd prior to the release >>> of 6.2. >> I'm pretty sure this change would break inetd's rpc service support and >> would change the startup order more significantly than I think is >> appropriate this late in the release cycle. >> >> -- Brooks > > What about adding a default port flag to /etc/defaults/rc.conf that > doesn't conflict with /etc/services? > > mountd_flags="-r -p 924" (or similar) > Doh! I just read the parent and see its regarding rpc.lockd and not mountd, my mistake. -Proto