When the preferred method of execution is an interactive process, the operator can start the NISH manager from the Linux command line, as shown in the following example:
[root@server ~]# nish-manager
2020-06-16 18:57:16.329 WARNING: Failed to read backup file: →
'/var/lib/nish-manager/connections.bkp'
2020-06-16 18:57:16.329 WARNING: Could not restore Db from: →
'/var/lib/nish-manager/connections.bkp'
2020-06-16 18:57:16.330 INFO: Server listening on [::]:57400To use the nish-manager command to start the NISH manager service, the user must have the required Linux permissions to bind the service to an IP address and TCP port.
The IP address and port number specified cannot conflict with an instance of the NISH manager service that is already running. This also applies if the running instance of the NISH manager service is running within systemd.
To run the NISH manager service in the background, append an ampersand (&) to the command. For information about additional command options, see Command options.
The displayed warnings about the connections.bkp file are the expected behavior for the first run because there is no backup file yet; see Backup file.
The nish-manager command can also be started as an interactive process using a configuration file that contains the required variables to start an instance of the NISH manager. For more information about configuration files, see NISH manager configuration files.
To start the NISH manager as an interactive process using a configuration file, append the filename to the nish-manager command as shown in the following example:
[root@server ~]# nish-manager myconfigfile.conf