Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia 
PreviousNextUp[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/ or, if the directory /var/run does not exist, in /etc/ssh2/ The PID file of the certificate validation daemon is stored in the same directory. This makes it easy to kill the appropriate daemon:

# kill `cat /var/run/`

or send signals to it:

# kill -SIGNAL `cat /var/run/`

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

PreviousNextUp[Contents] [Index]

[ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]

Copyright © 2010 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Copyright Notice


Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more