[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 >>

Starting the Server

When SSH Tectia Server has been installed from binaries, the server daemon and its certificate validation daemon are started automatically after installation and at boot time.

If the server needs to be started, stopped, or restarted manually, the start script can be used. If command-line options need to be used (for example, for debugging or to read in an alternate configuration file), the server can be started from the installation directory.

Using the Start Script

To start the sshd2 daemon type the following command:

• On Linux and Solaris:

  # /etc/init.d/sshd2 start
  

• On HP-UX:

  # /sbin/init.d/sshd2 start
  

• On AIX:

  # /etc/ssh2/sshd2 start
  

If the server is already running and you want to restart it, for example, to use a changed configuration file, type the following command:

• On Linux and Solaris:

  # /etc/init.d/sshd2 restart
  

• On HP-UX:

  # /sbin/init.d/sshd2 restart
  

• On AIX:

  # /etc/ssh2/sshd2 restart
  

Command-Line Options

If you want to use command-line options with sshd2 or ssh-certd, you have to start them in their installation directory.

The server daemon can be started by running the command:

# /usr/local/sbin/sshd2 [options]

Note: If the installation was successfully completed, sshd is a symbolic link to sshd2. If you also have Secure Shell 1.x installed, the SSH Tectia Server installation process modifies the existing link. If Secure Shell v1 compatibility is desired, sshd2 can be configured to execute sshd1 when the client only supports Secure Shell v1. However, it is recommended to use the sshd2 command because sshd may start an OpenSSH server.

The certificate validation daemon can be started by running the command:

# /usr/local/sbin/ssh-certd [options]

For more information, see the sshd2 and ssh-certd man pages.