systemd

On systems that support it, systemd is an option for managing SiLK services as of SiLK 3.23. The implementation of the various SiLK services as a systemd service is intended to provide an easy transition for those migrating from the init.d service implementations.

The following SiLK tools have associated systemd services:

• rwflowpack
• rwflowappend
• rwpollexec
• flowcap
• rwsender
• rwreceiver

When running a SiLK service for the first time, you must first modify the associated configuration file, e.g. rwflowpack.conf, with relevant parameters for your intended use. If you are upgrading from a previous version of SiLK, your configuration files will have persisted during the upgrade. The configuration files are typically found in /etc/sysconfig.

Once the configuration file is completed, starting any SiLK services is the same as starting any other systemd service:

# systemctl start rwflowpack.service

Checking the service status and stopping the service are also typical:

# systemctl status rwflowpack.service

and:

# systemctl stop rwflowpack.service

init.d

For systems that do not support systemd, the init.d service script is still available, however this capability is not present when installing via rpm.

Running a SiLK service using init.d is very similar to using systemd. The configuration file must be configured prior to first use with the parameters you want the service to use. The configuration file is typically located in /etc/sysconfig.

Once your configuration file is complete, you can start the SiLK service using the following command:

# service rwflowpack start

You can stop the service or check its status using:

# service rwflowpack stop

and

# service rwflowpack status

SiLK services also have one additional command, force-reload. This command is functionally identical to restart.