sshd reread

[himacs]

Hi gurus,

how to reread sshd process.Actually i dont want to stop the sshd by using /sbin/init.d/secsh start/stop.

If i use below command, any problem to existing ssh connections.

kill -SIGHUP `cat /var/run/sshd.pid`


please help on this...bit urgent


regards,
himacs

[Steven E. Protter]

Shalom,

The only way to do this is a start/stop

If its fast, existing connections will stay online and be serviced.

SEP

[TTr]

This very same question came up 5 days ago
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1349153

[kevin_m · Accepted solution]

I've done a 'kill -HUP ' several times and never lost connectivity, at least for the SSH session used to run the kill command.
- Kevin

[Mel Burslan]

/sbin/init.d/secsh stop
/sbin/init.d/secsh start

anything else is a crapshoot at best

[Steven Schweda]

> anything else is a crapshoot at best

Yeah. I'm sure that all that junk in the
manual like:

[...] sshd rereads its configuration
file when it receives a hangup signal,
SIGHUP, by executing itself with the
name and options it was started with,
e.g. /usr/sbin/sshd. [...]

was put there to lead the gamblers astray.


http://www.openbsd.org/cgi-bin/man.cgi?query=sshd&sektion=8

[Mel Burslan]

Books sometimes differ from the real life. Unfortunately inetd and sshd are the two products that I do not have confidence about re-reading the configuration file when received a SIGHUP signal, from my personal experience. You might chose to go by the book. That is a preference. Keeping the sshd down for a second or two does not mean a catastrophe on my end, so, I'll do how I chose to believe and Stephen, you do as you please.

[Steven Schweda]

> [...] I do not have confidence [...] from
> my personal experience.

And I have more confidence in my experience
than I have in yours.

> [...] you do as you please.

Thanks for your permission, Mr. Burlap.

[himacs]

Ha admin,

thanks for ur replies

i have used kill -SIGHUP `cat /var/run/sshd.pid` to reread. /var/run/sshd.pid file contains process id of parent ssh process.
it rereads sshd,so existing connections (child)
remains not killed.


regards

himacs

[Mel Burslan]

Even if you kill the sshd daemon, listening to port 22 on your system, it will not kill all the running ssh sessions. As long as it is down, your server can not accept any newly incoming connections. In my case this is about 2 to 3 seconds. Just wanted to let you know so that you do not have any misconceptions.