Date: 22 Jun 1999 11:02:55 +0200 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: Alex Charalabidis <alex@wnm.net> Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, Doug <Doug@gorean.org>, Sheldon Hearn <sheldonh@uunet.co.za>, freebsd-hackers@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: [Fwd: Re: misc/11796: Bad lines in 3.2-RELEASE inetd.conf] Message-ID: <xzp7lowli9s.fsf@flood.ping.uio.no> In-Reply-To: Alex Charalabidis's message of "Mon, 21 Jun 1999 16:57:35 -0500 (CDT)" References: <Pine.BSI.4.05.9906211508100.3966-100000@earth.wnm.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Alex Charalabidis <alex@wnm.net> writes: > On 21 Jun 1999, Dag-Erling Smorgrav wrote: > > The PR is wrong. Sheldon is right. It *does* work the way it ships. If > > he experienced problems, I bet the real bug was that he edited > > inetd.conf, HUPed inetd, and hit the "HUP clobbers the service table" > > bug. > I'll accept this as an explanation, since it sounds much more reasonable > than telling me I have no clue what I'm talking about. I edit inetd.conf > and HUP, like pretty much everyone else in the world and will keep HUPing > for many years to come. If it "clobbers the service table" on the odd > occasion and keeps it clobbered until you change the service's name, well > duh, please document it, I'm not psychic. :) We have no intention of documenting it, since the bug has been fixed. > If it also breaks on the > first machine I install 3.2-R on and coincides with my discovery of > aforementioned discrepancy, my guilt is limited to accepting an open > invitation to jump to conclusions and I will redeem myself through a > weekend penance of listening to the Spice Girls and watching Celine Dion. We're not *that* mad at you. Just ten 'power to the world' and five 'Mmmm-bop' will do. > > The alternative solution is to extend the format of inetd.conf to > > allow specifying the service name after the 'internal' keyword, so you > > could change /etc/services to read: > Dare I suggest something as straightforward as bringing inetd, inetd.conf, > /etc/services and the respective manpages into sync with each other and/or > reality? It's not the right solution. They'll only get out of sync again. The correct solution is to stop pretending /etc/services means anything to inetd except as a way to map service names to port numbers. It doesn't, and never did. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp7lowli9s.fsf>