Background
For those who don't know, systemd is a next-generation replacement for /sbin/init written by Lennart Poettering. While systemd supports traditional initscripts, service files are its native form of configuration. Service files have a structure similar to that of desktop files or Windows ini files. Their syntax is well documented in the manual pages.
Initscripts typically contain boilerplate code that checks whether the daemon is already running or figures out which process to kill when the daemon has to be stopped. Tools like start-stop-daemon help, but systemd reduces the syntax overhead to the minimum. This simplification occurs because service files specify what should be done, not how it should be done. I.e., unlike initscripts, they follow the declarative style and are not programs.
Simple services
Here is the simplest possible service file that starts VDE with options that work for me on my computer. Save it as /etc/systemd/system/vde.service:
[Unit] Description=Virtual Distributed Ethernet [Service] ExecStart=/usr/bin/vde_switch --tap tap0 --mode 0660 \ --dirmode 0750 --group qemu [Install] WantedBy=multi-user.target
Note the difference from a traditional init script: for simplicity, vde_switch is started in such a way that it doesn't become a daemon. In fact, it is possible to start real daemons that fork, you just have to tell systemd about that:
[Unit] Description=Virtual Distributed Ethernet [Service] Type=forking # The PID file is optional, but recommended in the manpage # "so that systemd can identify the main process of the daemon" PIDFile=/var/run/vde.pid ExecStart=/usr/bin/vde_switch --tap tap0 --mode 0660 \ --dirmode 0750 --group qemu \ --daemon --pidfile /var/run/vde.pid [Install] WantedBy=multi-user.target
The difference is in the way the dependencies are handled. If some other services depend on vde.service, then, in the first example, systemd will be able to run them as soon as it starts vde_switch. In the second example, systemd will wait until vde_switch forks. The difference matters, because vde_switch creates its control socket after starting, but before forking. So, in the first example, there is some chance that systemd will start something that tries to connect to the socket before vde_switch creates it.
Automatic restarts
Let's also add the proper dependency on the system logger and tell systemd to restart vde_switch if it crashes due to an uncaught signal (although it never happened to me):
[Unit] Description=Virtual Distributed Ethernet After=syslog.target [Service] Type=forking PIDFile=/var/run/vde.pid ExecStart=/usr/bin/vde_switch --tap tap0 --mode 0660 \ --dirmode 0750 --group qemu \ --daemon --pidfile /var/run/vde.pid Restart=on-abort [Install] WantedBy=multi-user.target
Now try to start and crash the daemon:
home ~ # systemctl start vde.service
home ~ # systemctl status vde.service
vde.service - Virtual Distributed Ethernet
Loaded: loaded (/etc/systemd/system/vde.service)
Active: active (running) since Tue, 04 Jan 2011 22:08:10 +0500;
15s ago
Process: 31434 (/usr/bin/vde_switch --tap tap0...,
code=exited, status=0/SUCCESS)
Main PID: 31435 (vde_switch)
CGroup: name=systemd:/system/vde.service
└ 31435 /usr/bin/vde_switch --tap tap0...
home ~ # kill -SEGV 31435
home ~ # systemctl status vde.service
vde.service - Virtual Distributed Ethernet
Loaded: loaded (/etc/systemd/system/vde.service)
Active: failed since Tue, 04 Jan 2011 22:11:27 +0500;
4s ago
Process: 31503 (/usr/bin/vde_switch --tap tap0...,
code=exited, status=0/SUCCESS)
Main PID: 31504 (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/vde.service
I.e., restarting didn't work. The system log tells us why:
Jan 4 22:11:27 home vde_switch[31504]: Error in pidfile creation: File exists
So, VDE has a bug in its pidfile creation. There are two ways how one can deal with this: either tell systemd to remove the PID file before starting vde_switch, or drop the PID file altogether (because vde_switch has exactly one process, there can be no confusion which process is the main one). Both ways work. Here is how to implement the first alternative:
[Unit] Description=Virtual Distributed Ethernet After=syslog.target [Service] Type=forking PIDFile=/var/run/vde.pid # Note the -f: don't fail if there is no PID file ExecStartPre=/bin/rm -f /var/run/vde.pid ExecStart=/usr/bin/vde_switch --tap tap0 --mode 0660 \ --dirmode 0750 --group qemu \ --daemon --pidfile /var/run/vde.pid Restart=on-abort [Install] WantedBy=multi-user.target
And here is the second alternative:
[Unit] Description=Virtual Distributed Ethernet After=syslog.target [Service] Type=forking ExecStart=/usr/bin/vde_switch --tap tap0 --mode 0660 \ --dirmode 0750 --group qemu \ --daemon Restart=on-abort [Install] WantedBy=multi-user.target
Configuration
Many initscripts come with configuration files that allow the user to customize how the daemon is started. For example, some users may want to pass the --hub argument to vde_switch, and others may want to enable the management socket. So, in Gentoo, the traditional configuration file for the initscript looks like this:
# load the tun module
VDE_MODPROBE_TUN="yes"
# virtual tap networking device to be used for vde
VDE_TAP="tap0"
# mode and group for the socket
VDE_SOCK_CHMOD="770"
VDE_SOCK_CHOWN=":qemu"
# This is the actual options string passed to VDE.
# Change this at your own risk.
VDE_OPTS="--tap ${VDE_TAP} -daemon"
Systemd service files typically use the EnvironmentFile key to provide users with a file where they can put their preferences regarding the service.
Traditional initscripts source their configuration files. Thus, any syntax construction supported by /bin/sh will work in the configuration file. In the example above, we see comments, assignment of values to variables, and reusing the values in later assignments. Systemd uses a different syntax from bash, so please resist the temptation to reuse the same configuration file for the traditional initscript and the service file. Resist even though some service files in the Gentoo systemd overlay do use the same configuration files as the corresponding traditional initscripts -- they are just buggy. Let me explain this in more detail.
Of course, the configuration file example above is not suitable for systemd because variable interpolation is not supported in systemd environment files. But let's suppose that we want to invent something that is suitable both as a bash script fragment and a systemd environment file, and still allows the user to configure vde_switch according to his wishes.
Let's focus on the VDE_OPTS variable only, as it is the only thing that matters. Indeed, module loading can be done directly by systemd (man modules-load.d), and the options related to the socket group and octal permissions can be expressed using vde_switch command line options, as illustrated in the examples above. Since the value of the VDE_OPTS variable can contain spaces, we have to quote it if we want bash to be able to understand what we mean:
VDE_OPTS="--tap tap0 --mode 0660 --dirmode 0750 --group qemu"
Without quotes, bash would interpret this as follows: with the variable VDE_OPTS that has value "--tap" in the environment, start the "tap0" process and pass 6 parameters to it. So, quotes are essential here.
Let's try to use this variable from the service file. We want it to be split by the spaces, so that each part becomes a separate vde_switch parameter. So, according to the systemd.service manpage, we have to use the $VDE_OPTS form, not ${VDE_OPTS}. So here is what we have:
[Unit] Description=Virtual Distributed Ethernet After=syslog.target [Service] Type=forking EnvironmentFile=/etc/conf.d/vde2 ExecStart=/usr/bin/vde_switch --daemon $VDE_OPTS Restart=on-abort [Install] WantedBy=multi-user.target
Result: no "tap0" interface and wrong permissions on the control socket. This happened because quotes play a special role in systemd environment files, different from their role in bash scripts. For systemd, they mean that the spaces inside them should not be treated as argument separators. So, all the arguments in $VDE_OPTS were passed to vde_switch as one long argument. No surprise that it didn't work.
In fact, the service file is correct. Its configuration just can't be made compatible with bash, because it is in a different language. The service works with the following configuration file (alas, incompatible with bash):
VDE_OPTS=--tap tap0 --mode 0660 --dirmode 0750 --group qemu
Conclusion
Let's hope that all of the above will get you started writing your own systemd service files. Since there are many initscripts in Gentoo still not converted, the project needs your help.
Thanks
The following people from #systemd IRC channel on freenode provided me with valuable support: MK_FG, zdzichuBG, miti1.
