From: Alexander von Gernler (grunkpestilenz.org)
Date: Mon Jan 03 2005 - 07:40:48 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sun, Jan 02, 2005 at 11:57:41PM +0100, Ingo Schwarze wrote:
> > Are there some other admins out there who had that problem already? :)
>
> Definitely yes.
>
> The following is a quite common mistake:
>
> rootfaraway # vi /etc/ssh/sshd_config
> rootfaraway # kill -HUP `cat /var/run/sshd.pid`
> rootfaraway # exit
> luserhome $ ssh faraway
> ssh: connect to host faraway port 22: Connection refused

Taken from sshd(8):

    -t Test mode. Only check the validity of the configuration file and
         sanity of the keys. This is useful for updating sshd
         reliably as configuration options may change.

Apart from using that, you could easily have checked your process list
for your master sshd, just as you wrote. If there is none because you
borked the configuration, exiting your shell is not really the smart
thing to do.

Permanently running a 2nd sshd just for this purpose is plain overkill.

--
Alexander "grunk" von Gernler PGP-Key 0xEBC27515
https://openbsd.informatik.uni-erlangen.de - Free, functional, secure.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]