Server command-line interface
The server command-line interface (CLI) provides a low level interface to run server process. It can be used by higher level tools like the administrative CLI (see the chapter The administrative command-line interface) or by the user directly.
You can use the server CLI to start nevisLogRend without the involvement of other system components such as systemd.
You find the server script at /opt/nevislogrend/bin/nevislogrend-server. It provides the following command line options:
-c, --config PATH
Required. Path to the configuration file nevislogrend.properties.
-n, --name NAME
Unique name for that Nevis component node. Overrides the value of the property
server.name
(in the nevislogrend.properties file).-p, --port PORT
The HTTP/S port to listen on. TLS must be configured in the config file and not as an argument. Overrides the value of the property
server.port
(in the nevislogrend.properties file).-H, --host HOST
The HTTP/S host to bind on. By default binds on all IPv4 and IPv6 interfaces. Overrides the value of the property
server.host
(in the nevislogrend.properties file).--log-config PATH
Log configuration file to be used. If a log configuration is provided, nevisLogRend will use the given configuration file to determine how logging should behave. If no configuration file is provided, nevisLogRend will log to the console by default.
-V, --version
Display version and exit with status code 0.
-h, --help
Show complete and detailed usage and exit with status code 0.
Command-line arguments always override properties in the logrend.properties file.
Example of using the server CLI
To start an existing nevisLogRend instance named "default" without using systemd to manage the service, execute the following commands:
# set working directory
cd /var/opt/nevislogrend/default
/opt/nevislogrend/bin/nevislogrend-server --config /var/opt/nevislogrend/default/conf/logrend.properties --log-config /var/opt/nevislogrend/default/conf/log4j.xml