The NISH manager is installed as a Linux systemd service, which for security reasons is installed as follows:
in a stopped state (not running)
disabled (does not start automatically on reboot)
The operator can start and enable the NISH manager within the systemd service at the same time or independently.
To start the NISH manager service within the systemd service and ensure that it restarts when the service or workstation is rebooted, issue the following commands:
[root@server ~]# systemctl enable nish-manager --now
The enable operation ensures that the NISH manager is started on system boot. The --now option ensures that the NISH manager service starts immediately.
It is also possible to perform the start and enable operations independently. To do so, issue the following commands:
[root@server ~]# systemctl start nish-manager
[root@server ~]# systemctl enable nish-manager
To disable and stop the NISH manager within the systemd service, issue the following command:
[root@server ~]# systemctl disable nish-manager --now
The disable operation ensures that NISH manager is no longer started upon reboot. The --now option ensures that the NISH manager service stops immediately.
To perform the stop and disable operations independently, issue the following commands:
[root@server ~]# systemctl stop nish-manager
[root@server ~]# systemctl disable nish-manager
The following example shows the nish-manager.log output file after startup. After the trademark, legal, and disclaimer information, NISH displays the following:
2020-06-16 18:52:47.952 WARNING: Failed to read backup file: →
'/var/lib/nish-manager/connections.bkp'
2020-06-16 18:52:47.952 WARNING: Could not restore Db from: →
'/var/lib/nish-manager/connections.bkp'
2020-06-16 18:52:47.953 INFO: Server listening on [::]:57400
Multiple NISH manager systemd services can be started simultaneously and each one can maintain its own configuration in a NISH manager configuration file; see NISH manager configuration files for more information.
By default, when the NISH manager is started as a systemd service (for example, using systemctl start nish-manager) it reads from the /etc/nish-manager/nish-manager.confconfiguration file, if this file exists. If this file does not exist, the default values are used.
The NISH manager can also be started by systemd using the values specified in a specific NISH manager configuration file. This configuration file must be located in the /etc/nish-manager directory and .conf must be appended to the file extension.
To start a systemd instance of the NISH manager using a configuration file, issue the commands as shown in the following example:
[root@server ~]# systemctl start nish-manager@example1
[root@server ~]# systemctl enable nish-manager@example1
The start command runs the service and reads from the configuration filename provided in the command after the @ symbol. In this example, the nish-manager Linux service starts and reads the configuration file /etc/nish-manager/example1.conf for its instantiation variables.
These commands can be combined together as shown in the following example:
[root@server ~]# systemctl enable nish-manager@example1 --now
Another systemd NISH manager service can be started by adding the configuration filename (without the .conf file extension) after the @ symbol. In the following example, a NISH manager service instance starts and reads the /etc/nish-manager/example2.conf configuration file for its instantiation variables:
[root@server ~]# systemctl enable nish-manager@example2 --now
Multiple systemd NISH manager services can run in parallel, if the IP address and TCP port combination bindings do not overlap.