Date: Tue, 17 Oct 2006 09:39:47 -0500 From: Brooks Davis <brooks@one-eyed-alien.net> To: Trond Endrest?l <Trond.Endrestol@fagskolen.gjovik.no> Cc: re@freebsd.org, FreeBSD stable <freebsd-stable@freebsd.org> Subject: Re: Ensuring inetd is started before any RPC services Message-ID: <20061017143947.GA68977@lor.one-eyed-alien.net> In-Reply-To: <20061017082319.I27675@ramstind.fig.ol.no> References: <20061017082319.I27675@ramstind.fig.ol.no>
next in thread | previous in thread | raw e-mail | index | archive | help
--tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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=20 > services have occupied the well-known ports for other non-RPC based=20 > services. Last week rpc.lockd on one of my systems got hold of TCP=20 > port 995, leaving inetd unable to start any pop3s services. >=20 > The easy cure is to add this line >=20 > # BEFORE: rpcbind >=20 > to /etc/rc.d/inetd. >=20 > You might want to consider fixing /etc/rc.d/inetd prior to the release=20 > 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 --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFNOsyXY6L6fI4GtQRAt1PAJ9vmY0nGNKduSA8F5A3fkfNgESgZgCfeINn KJH7opmjRi5ijNW47bPzJ9c= =k1Sc -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061017143947.GA68977>