[Contents] [Index]

About This Document>>     Introduction to SSH Secure Shell >>     Configuring SSH Secure Shell >>     Authentication >>     Log Messages >>     Using SSH Secure Shell >>         Using the Secure Shell Server Daemon (sshd2)>>             Manually Starting the Secure Shell Server Daemon             Automatically Starting the Server Daemon at Boot Time             Operation of the Server Daemon             Resetting and Stopping the Server Daemon             Daemon Configuration File and Command-Line Options             Subsystems         Using the Secure Shell Client (ssh2)>>         Using Secure Copy (scp2)         Using Secure File Transfer (sftp2)         Using Authentication Agent (ssh-agent2, ssh-add2)     Tool Syntax>>     Technical Specifications >>

Resetting and Stopping the Server Daemon

When the Secure Shell daemon is started, its process identifier (PID) is stored in /var/run/sshd2_22.pid or, if the directory /var/run does not exist, in /etc/ssh2/sshd2_22.pid. This makes it easy to kill the appropriate daemon:

kill `cat /var/run/sshd2_22.pid`

or send signals to it:

kill -SIGNAL `cat /var/run/sshd2_22.pid`

The Secure Shell daemon handles signals like inetd: you can send it a SIGHUP signal to make it reread its configuration file. The daemon can be stopped by sending the SIGKILL signal.

All sshd processes can be terminated if needed. This should be done only when root is logged in locally, as the server process for the root user who is remotely logged in will also be terminated. Another option is to start a new sshd2 daemon on a different port before terminating sshd processes:

sshd2 -p 1234

Only the sshd processes (e.g. /usr/local/sbin/sshd) will be terminated:

killall sshd