I am writing my first
systemd unit file.
Type, there are a few choices:
simple, etc. I have read the Redhat Documentation on this topic (Table 9.9) , but still am not sure when I should use which option.
Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up.Sign up to join this community
When you start the service manually from the command line (without using the
nohupprefix command or the
& suffix to run it in the background, or in other words, just run the command you would put on the
ExecStart= line of the
.service file), what happens?
a) If the service starts and keeps running, and the prompt does not return until you press Control-C or stop the service in some other way: then
Type = simple is the right choice.
b) If the prompt returns but the service keeps running in the background (i.e. the service daemonizes itself on its own), then
Type = forking is the right choice.
c) If the service does its job and returns to the prompt without leaving anything running (i.e. the service just adjusts some kernel settings, sends a command to something else or does something similar), then
Type = oneshot is probably the right choice. In this case,
ExecStart of the service might be the command to "set" something, and
ExecStop would be the corresponding command to "unset" it. This type usually benefits of
RemainAfterExit=true, so systemd will keep track of the "state" of this service according to whether the thing was most recently "set" or "unset".
Type values are special cases. For example, if the service utilizes a D-Bus connection, then
Type = dbus might be the best choice. It makes
systemd aware of the fact, and then systemd will track this service (and anything that depends on it) by the presence of this service on the D-Bus.
Type = notify, the process must be able to connect to Unix socket specified in environment variable
$NOTIFY_SOCKET and to report its status by writing messages to that socket whenever necessary. Also, the service file should specify the
NotifyAccess option to grant access to the notification socket as appropriate.
There is a command-line utility
systemd-notify and a C library function
sd_notify(3) you may use to send these messages, but if neither of those is suitable to your requirements, you can just implement your own message sender. The messages required are very simple, and look like shell variable assignments: for example, to notify that the service has successfully completed startup and is ready to serve any incoming requests, the service should send the string equivalent to the output of
printf "READY=1\n" to the socket. See
man 3 sd_notify for more details on the recognized messages.
Note: many service applications designed to be portable to many Unix-style systems may behave as b) by default, but can be made to work like a) by adding an option (usually described as "don't fork", "keep running in foreground", "don't daemonize" or similar). In that case, if the option has no other side effects, then adding the option and using the a)-type behavior would be preferable for