Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!caen!hookup!solaris.cc.vt.edu!news.mathworks.com!tank.news.pipex.net!pipex!oleane!jussieu.fr!math.ohio-state.edu!magnus.acs.ohio-state.edu!lerc.nasa.gov!purdue!news.bu.edu!mi From: mi@cs.bu.edu (Mikhail Teterin) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: /etc/services Date: 24 Aug 1995 13:04:13 GMT Organization: Computer Science Department, Boston University, Boston, MA, USA Lines: 37 Message-ID: <41htce$91l@news.bu.edu> References: <41gtu9$knu@news.bu.edu> <87virn9aoy.fsf@hrothgar.mindspring.com> NNTP-Posting-Host: csb.bu.edu X-Newsreader: TIN [version 1.2 PL2] Some time ago (24 Aug 1995 00:39:57 -0400) honorable Robert Sanders, residing at rsanders@mindspring.com wrote: |Just to reach greater clarity, could you show how you expected it to |work? My impression was, that when inetd hears a connection attempt on the port it looks at /etc/services to find out which server to wake up (say telnet). Then it goes and looks for parameters of that server (including the path to the executable) in /etc/inet.conf. So, I expected the relation between service<->port to be (possibly) one-to-many, not one-to-one as it appears to be (and not many-to-one as it does not make sense to me). |> I tried to put plain telnet on port 80 (as well as the original, 23), |> and it did not work until I renamed it to, say, banana, and explained |> in /etc/inetd.conf what banana is -- same as telnet. |> telnet stream .................... /usr/libexec/telnetd |> banana stream .................... /usr/libexec/telnetd |> Is that a bug or a feature? Why can not inetd accept same service |> for different ports? Or if that's a feature, why does not it complaint |> somewhere? |Um, the leftmost argument specifies what port to put the service on. |"telnet" causes inetd to look in /etc/services to find the port # |(23), and "banana" causes inetd to look in /etc/services and find, |presumably, port 80. If you have two lines that begin with "telnet", |you have two definitions for port 23, which is in error. Aga, that explains the current behavior, but does not seem reasonable... Why can not same service sit and wait for few ports? Seems like a design problem to me... -mi -- -- Why is that 2 o'clock all the time?! -- It is a manometer!!!