[Contents] [Index]

About This Document >>     Installing SSH Tectia Server >>     Getting Started >>         Location of Installed Files >>         Starting and Stopping the Server >>             Starting the Server             Stopping the Server         Operation of the Server >>         SSH Tectia Server (T) >>         SSH Tectia Server (A) >>         SSH Tectia Client >>         Examples of Use     Configuration >>     Authentication >>     Application Tunneling >>     Troubleshooting >>     Man Pages     Advanced Options >>     Log Messages >>

Stopping the Server

Using the Stop Script

To stop the sshd2 daemon type the following command:

• On Linux and Solaris:

  # /etc/init.d/sshd2 stop
  

• On HP-UX:

  # /sbin/init.d/sshd2 stop
  

• On AIX:

  # /etc/ssh2/sshd2 stop
  

Using the kill Command

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. The PID file of the certificate validation daemon ssh-certd.pid is stored in the same directory. 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 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 the daemon processes. This can be done with the following command:

# /usr/local/sbin/sshd2 -p 1234