On Mon, 21 Jun 1999 11:12:26 MST, Doug wrote:

>       Can you point out exactly what part of the man page that you are
> referring to that contradicts what the inetd man page says? Have you
> checked the actual code for inetd to verify that it will work with
> services aliases? 

Certainly. From services(5):

     The services file contains information regarding the known services
     available in the DARPA Internet.  For each service a single line should
     be present with the following information:

           official service name
           port number
           protocol name
           aliases

We wouldn't be straying too far from reality if we interpretated the
word "alias" as "another name for".

We now look at /etc/services and see:

auth            113/tcp    ident tap    #Authentication Service
auth            113/udp    ident tap    #Authentication Service

We read from this that each of "ident" and "tap" is "another name for"
"auth".

We now look et /etc/inetd.conf, where we find:

#ident  stream  tcp     wait    kmem:kmem       /usr/local/sbin/identd identd 
-w -t120

I uncommented this line a few years ago and haven't had a problem with
my ident service that I could think of.

>       In my experience, and in the experience of the PR poster it *is*
> necessary to use the canonical name of the service, however if you can
> check the code, test it thoroughly and determine that inetd works
> perfectly well with aliases, then feel free to change the man page for
> inetd. 

Since the manpage supports my experience thus far, I really can't see
how you'd put the burden of proof on me. :-)

Let's see a "How-To-Repeat" of somewhat more substance than "Try running
identd without having noticed the glitch".

Ciao,
Sheldon.


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to