Inetd.conf and RH 7.0

[chy at genuity.com (Chuck Young)]

Speaking of inetd.conf, what happened to it in RH 7.0?

find / -name "inetd.conf" -print yields zilch

Admittedly, my free time is moving into negative numbers and I have not done
much reading, but I can't figure out how to not run ftpd anymore...

----------------------
Chuck Young
ISE, New England Region
Genuity, Inc.
----------------------

-----Original Message-----
From: owner-discuss at blu.org [mailto:owner-discuss at blu.org]On Behalf Of
Sheldon Dubrowin
Sent: Tuesday, February 06, 2001 9:15 AM
To: Phil Buckley
Cc: discuss at blu.org
Subject: Re: Can't access remote machine anymore


Maybe SSHD stopped running.  I was at SANS last week and they recomended
running an SSHD on the "regular" port, port 22, but also putting SSHD in
inetd.conf on some other port in case the "regular" SSHD fails, inetd.conf
will start one up for you.  It is not usually run from inetd because it can
take a few seconds to start the daemon and that is usually unacceptable, but
in this type of emergency type case, where you would have to drive to the
machine, it is better than nothing.  ;-)  Hope this helps you Phil.

	Shel

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).