systemd: Don't fear change
Published: 25-03-2015 | Author: Jonathan Roberts | Text only version of this article
❗ This post is over eight years old. It may no longer be up to date. Opinions may have changed.
This article was originaly published in Linux Voice, issue 1, April 2014. This issue is now available under a Creative Commons BY-SA license. In a nutshell: you can modify and share all content from the magazine (apart from adverts), even for commercial purposes, providing you credit Linux Voice as the original source, and retain the same license.
This remix is converted manually to Markdown and HTML for ease of archiving and copy-pasting.
Recently I removed all Google Ads from this site due to their invasive tracking, as well as Google Analytics. Please, if you found this content useful, consider a small donation using any of the options below:
I'm developing an open source monitoring app called Leaf Node Monitoring, for windows, linux & android. Go check it out!
Consider sponsoring me on Github. It means the world to me if you show your appreciation and you'll help pay the server costs.
You can also sponsor me by getting a Digital Ocean VPS. With this referral link you'll get $100 credit for 60 days.
Other converted Linux Voice articles can be found here.
The init replacement for RHEL 7 and SUSE Enterprise Linux 12.
systemd: Don't fear change
The arrival of a new Linux init system has been a long time coming. It was back in 2006 that Upstart was introduced to Ubuntu, and around the same time that Fedora and others also started experimenting with new init systems.
The reasons then are much the same as the reasons now - sysvinit is old and doesn't do everything a modern distribution needs it to. More specifically:
- sysvinit can't take account of hot-pluggable hardware devices and filesystems, such as network mounts or USB sticks.
- sysvinit doesn't provide sufficient supervision of processes, allowing double forked processes to become orphaned.
- sysvinit can't parallelise boot services effectively, so it is slow.
- sysvinit startup scripts are difficult to write, difficult to debug and can't easily be shared between distributions - the Sendmail init script is over 1,000 lines long!
Systemd fixes these problems and introduces a number of new features that make the case for it even more compelling. Rather than explaining in great detail how systemd works or how it fixes these problems (there's plenty of information on that in http://0pointer.de/blog/projects/systemd.html, we're going to take a look at a few key features of systemd that might make sysadmins look forward to systemd, rather than dread having to learn a new tool.
Configuration file format
As mentioned above, in sysvinit systems, configuration of services was complex
and error-prone. They were usually configured through a combination of arcane
Bash scripts in
/etc/init.d and some environmental settings in
/etc/defaults. These init scripts often did awful amounts
of work, such as echoing service status to the console and managing lock files,
which were repeated in almost every init script.
Systemd removes the need for much of the complexity in these init scripts by handling service status echoes and suchlike itself. This means it can switch complex procedural Bash code for a clear, declarative configuration file. For example, here's the configuration for the syslog service on my Fedora system:
[Unit] Description=System Logging Service [Service] EnvironmentFile=-/etc/sysconfig/rsyslog ExecStart=/sbin/rsyslogd -n $SYSLOGD_OPTIONS Sockets=syslog.socket StandardOutput=null [Install] WantedBy=multi-user.target Alias=syslog.service
All of the configuration options available in these files are extremely well
documented (systemd as a whole has some of the best docs around) - see
man systemd.service for details.
What's more, if you had to modify a sysvinit file, you'd have to be careful when
it came to package upgrades etc that your changes wouldn't get overwritten. With
systemd, unit files get packaged into
/usr/lib/systemd/system, but if you want
to replace the default with your own, you can put them in
and whatever is there will take precedence over the defaults.
You can even include other unit configuration files in yours, so you can easily extend the default configuration:
include /usr/lib/systemd/system/nfs-secure.service #extra conf goes here
Why would you want to extend a service configuration like that? Well, systemd launches all processes inside their own cgroup (and all processes spawned from this end up in the same cgroup - this is also useful as it stops double forking processes from orphaning themselves), so you can take advantage of this to use cgroups to limit the resources that each process (and its child processes) can consume.
Systemd not only makes this possible by the way it spawns processes, but it also
makes it easy by exposing many of the most common bits of functionality in
configuration directives. For instance, you could limit the amount of CPU a
process gets by dropping in a new unit configuration file to
/etc/systemd/system and adding:
By default, systemd gives all processes (well, cgroups), an equal share of the
processor (1024). By setting
CpuShares to 200, you're restricting this process
to about 20% of CPU time. What's more, this isn't applied just to the parent
process but to all child processes. So if you have Apache running with many
hundreds of spawned CGI processes, this would restrict all of those processes to
about 20% of CPU time.
With the configuration file in place, you'd just need to tell systemd to reload
systemctl daemon-reload, and then restart the service, with
systemctl restart httpd.service, for example.
You can also set memory limits (
MemoryLimit) and IO limits (
man systemd.resource-control for further details. There are also any
number of security settings that can be put in the configuration files like
For example, you can restrict a service from accessing a particular device, make
individual directory trees inaccessible or read-only, create a private
directory for a service or even stop a service, and all its child processes,
from accessing the network.
In the example below, we've configured a service to have a private /tmp directory. See how simple it is:
Another aspect of systemd is that it collects all output from processes it
starts - whether that's through
syslog() calls, messages emitted to
STDERR, initial RAM disk or kernel messages. It does this through one of
its components, journald.
To see the contents of the logs, you can just type
journalctl as root and
you'll get the results displayed, just as if you were looking at the contents of
/var/log/messages or similar. This default view gives you some simple
improvements over the traditional techniques, however. Error and higher priority
messages are in red, notice and warning are bold, timestamps are in your local
These are fairly cosmetic improvements. What sets journald apart is that the logs are kept on disk in a binary format, which means that the journal entries can be indexed on all fields, making them quick to search and easy to filter. For example:
journalctl PRIORITY=7 -since=yesterday
Will show all messages of debug priority received by the journal since
yesterday. If you tried to do this with standard syslog messages or the like,
you'd have to concoct your own
awk command, or hook it in to a
There are loads of fields on which you can filter that come direct from the messages themselves, as well as a lot of metadata that the journal inputs in to each log message itself, including SELinux context, hostname, transport etc.
To see the full details, you can read
Journalctl even features tab completion of possible field names, so you can get a quick look too by typing
There are many other great features in systemd that, if you take the time to look around, will make your life as a sysadmin better.
We hope this article has at least given you the motivation to take a closer look.Tags: articles , centos , init , linux-voice , linux-voice-issue-1-2014 , systemd , upstart