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 >>
    Configuration >>
    Authentication >>
    Application Tunneling >>
    Troubleshooting >>
    Man Pages
    Advanced Options >>
        Installing SSH Tectia Server from the Source Code
            Automating Server Startup
        Configuring TCP Wrappers >>
    Log Messages >>

Automating Server Startup

If you have installed SSH Tectia Server from binaries, sshd2 by default starts automatically at boot time. However, if you have installed from source code, you need to modify your system to enable automatic startup.

In the following sections, two different methods for starting the Secure Shell daemon at boot time are introduced. If neither of these methods work on your system, consult your operating system documentation on how to start services at boot time.

Starting from /etc/rc.d/rc.local

In order to start sshd2 automatically at boot time on operating systems based on System V, the startup script sshd2 should be located in the /etc/rc.d/init.d directory, and there should be symbolic links to the sshd2 startup script in /etc/rc.d/rc?.d, where "?" is the run level. You can either add these links manually or use chkconfig.

Note: chkconfig is only available on Red Hat distributions. With SuSE, add the symbolic links manually.

If you want to use chkconfig, check that the first lines in sshd2 are similar to the following:

#!/bin/sh
#
# Author: Sami Lehtinen <sjl@ssh.com>
#
# sshd2    This shell script takes care of starting 
#          and stopping sshd2.
#
# chkconfig: 345 34 70
# description: Secure Shell daemon
#

This means that sshd will be started in run levels 3, 4 and 5, its starting priority is 34, and its killing priority is 70. You can choose the run levels and priorities as you want as long as sshd is started after the network is up.

After adding the links manually or giving the command

$ chkconfig --add sshd2

you should have the links in /etc/rc.d/rc?.d, similar to

lrwxrwxrwx 1 root  root  14 Aug 16 10:07  S34sshd -> ../init.d/sshd
lrwxrwxrwx 1 root  root  14 Aug 16 10:07  K70sshd -> ../init.d/sshd

Starting from /etc/rc.local

On BSD-based operating systems, you have to add a similar line to the following to the rc.local file in the /etc directory:

echo "Starting sshd2..."; /usr/local/sbin/sshd2

After this, the server daemon will start automatically at boot time.

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