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) -Proto _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"