Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Jan 2001 02:23:59 -0800 (PST)
From:      opentrax@email.com
To:        billf@mu.org
Cc:        peter@netplex.com.au, dwmalone@maths.tcd.ie, bugs@FreeBSD.ORG, doc@FreeBSD.ORG
Subject:   Re: docs/24307: man page for inetd(8) missing /etc/protocols in FIL ES section
Message-ID:  <200101151024.CAA02883@spammie.svbug.com>
In-Reply-To: <20010115031332.A61857@elvis.mu.org>

next in thread | previous in thread | raw e-mail | index | archive | help


On 15 Jan, Bill Fumerola wrote:
> On Mon, Jan 15, 2001 at 01:09:27AM -0800, opentrax@email.com wrote:
>> > There is no need.  There is no point adding a '/etc/protocols' to the FILES
>> > list since inetd does not use the '/etc/protocols' file.  At best it would
>> > be misinformation.
>> > 
>> Wait. How is this misinformation? I must be missing something.
> 
> Because /etc/protocols doesn't have to exist, could be wrong, etc and it doesn't
> make a difference to inetd, because it _does not use it_.
> 
Yes, I got that part. I'm sorry I was not clear.
The question then should be: if what you are saying
is correct, then the man page is wrong and we should
remove or correct the part about /etc/protocols.
The man page clearly says:

"The protocol must be a valid protocol as given in /etc/protocols."

As a matter of fact, the man page for 4.2 say so also.

Now being even more annoying, decided to check the code.

  "$FreeBSD: /c/ncvs/src/usr.sbin/inetd/inetd.c,v 1.80.2.2 2000/10/24 19:18:29 dwmalone Exp $";

Comments in the code says:

	protocol	must be in /etc/protocols

Granted, I don't see where it is used, but I don't see where
/etc/services is used either.

If you are correct, then the man pages still needs a correction.
In either case, I need to know what to put.

Your assitance appreciated.

				Jessem.





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?200101151024.CAA02883>