>
> inetd isn't the only option. There's also xinetd and rlinetd. rlinetd
> uses a different type of config file(s). Then there's tcpserver from
> Dan Bernstein's ucspi-tcp package. You run one invocation of tcpserver
> for each service you wish to support.
>
> None of these are available with a fresh RH install. However the point
> I'm making is that, unless you know a machine's history, do not
> automatically expect things to be "standard". Not having an
> /etc/inetd.conf may not necessarily be a problem - some people
> consider it an advantage :)
>
Agreed. But not on a fresh install !!! There is no history to reckon with
and it should have installed inetd and the regular stuff. As the user
mentioned, he did a fresh install.
-- Aravind
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
