Date: Mon, 21 Jun 1999 15:00:05 -0700 (PDT) From: Alex Charalabidis <alex@wnm.net> To: freebsd-bugs@FreeBSD.org Subject: Re: [Fwd: Re: misc/11796: Bad lines in 3.2-RELEASE inetd.conf] Message-ID: <199906212200.PAA14141@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/11796; it has been noted by GNATS. From: Alex Charalabidis <alex@wnm.net> To: Dag-Erling Smorgrav <des@flood.ping.uio.no> Cc: 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] Date: Mon, 21 Jun 1999 16:57:35 -0500 (CDT) On 21 Jun 1999, Dag-Erling Smorgrav wrote: > Doug <Doug@gorean.org> writes: > > "It doesn't work with the conf file that came with the system, but > > it does work if I change the conf file to match the documentation" is > > pretty good content in my book. Obviously he doesn't include information > > on how to repeat the problem in a verifiable way, but that doesn't (in my > > book anyway) invalidate the PR. > Whether the PR is valid or not (sure, I admit I've submitted better ones...), the discrepancy between /etc/services and inetd.conf is obvious to even the less trained eye. Doug's point about not expecting new users to RTFS applies to everyone else too when there should be no need to do so in the first place, especially with something as old hat as inetd. > 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. :) 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. > The right way to fix the documentation is simply to mention what inetd > thinks the canonical names are. > > 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? There's the remaining $.01 I owe, you now have my two cents. Regards -ac Alex Charalabidis WebNet Memphis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906212200.PAA14141>