On Tue, Oct 17, 2006 at 05:14:22PM +0200, Trond Endrest?l wrote: > On Tue, 17 Oct 2006 09:39-0500, 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. > > Yes, I see your point. > > I guess we who never run any RPC services through inetd must make this > change ourself, and it's relatively easy to maintain this change when > using mergemaster after each installworld. One size does not fit all, > not in this case.
It's clear to me that we need a better way to specifying which ports services that want an arbitrary port can use. That's probably the long term solution. -- Brooks
pgpdyR40ReYwX.pgp
Description: PGP signature
