Doug <d...@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.
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 urge you, again, to try and understand my point. There is no > reason to have the man page and the example conf file out of synch. Also, > as Dag-Erling pointed out, the real problem is much deeper than either, > however bringing the documentation up to date *should* be a priority > regardless of how many of the other problems you choose to fix. 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: fooglorb 113/tcp and inetd.conf to read: fooglorb stream tcp nowait root internal ident and inetd would know what service to provide on port 113, even if /etc/services doesn't call it 'ident'. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
