begin Tin Le quotation:
> There is at least another situation where it does make sense to run sshd
> under inetd, besides the one you mentioned.
>
> That is where the box is in a location far away (physically) and you want
> to make sure that if the (OS)network layer works, you can access it via
> ssh.
>
> I am in such a situation now. I have a server in cabinet at ISP far away.
> Their staff rebooted my box without permission (I am moving the box soon),
> and it did not come up correctly. I don't know what the exact problem is,
> since I can't ssh in. However, it is "up enough" that ftp and web work.
> But since sshd is started late in rc.local instead of using inetd, I can't
> login! Grrrr. It probably is hung somewhere in rc.local.
Well, but that begs the question of why you would start sshd late in the
startup process, i.e., in rc.local. On a SysVInit system, one ordinarily
has a separate startup script, early in the normal runlevel.
This has the advantage, come to think of it, of avoiding having sshd shut
down and starting up in lockstep with inetd. (Yes, the currently
running instance doesn't stop just because inetd does, but that's beside
the point.)
--
Cheers, "Censeo Toto nos in Kansa esse decisse."
Rick Moen -- D. Gale
rick (at) linuxmafia.com
