Create Systemd Init Service Unit

One of the systemd feature is to create the init service unit file for starting your program automatically at different run levels without manual and explicit call out. The full documentation is available at: https://wiki.debian.org/systemd/Services. This section guides you on how to write such unit file.

File Properties

This section covers all the file properties.

Service Type

Now you need to determine the service types.

• simple - basic startup based on ExecStart= is specified but neither Type= nor BusName= are. the unit started immediately after the main service process has been forked off. Note that this means systemctl start command lines for simple services will report success even if the service's binary cannot be invoked successfully (for example because the selected User= doesn't exist, or the service binary is missing).
• exec - The exec type is similar to simple, but the service manager will consider the unit started immediately after the main service binary has been executed. The service manager will delay starting of follow-up units until that point. Note that this means systemctl start command lines for exec services will report failure when the service's binary cannot be invoked successfully (for example because the selected User= doesn't exist, or the service binary is missing).
• forking - it is expected that the process configured with ExecStart= will call fork() as part of its start-up. The parent process is expected to exit when start-up is complete and all communication channels are set up. The child continues to run as the main service process, and the service manager will consider the unit started when the parent process exits.
• oneshot - Behavior of oneshot is similar to simple; however, the service manager will consider the unit started after the main process exits.
• dbus - Behavior of dbus is similar to simple; however, it is expected that the service acquires a name on the D-Bus bus, as configured by BusName=.
• notify - it is expected that the service sends a notification message via sd_notify(3) or an equivalent call when it has finished starting up.
• idle - Behavior of idle is very similar to simple; however, actual execution of the service program is delayed until all active jobs are dispatched.