systemd is a modern sysvinit & RC replacement for Linux systems. It is supported in Gentoo as an alternate init system.
- 1 Pre-installation Configuration
- 2 Installation
- 3 Booting with systemd
- 4 Post Installation Configuration
- 5 Services
- 6 Troubleshooting
- 7 See Also
- 8 External resources
systemd makes use of many modern Linux kernel features. Right now, the lower bound on kernel version is set in the ebuild to 2.6.39. In recent versions of sys-kernel/gentoo-sources, there is a convenient way of selecting the mandatory and optional Kernel options for systemd:
If you wish to configure your Kernel options manually, or do not use sys-kernel/gentoo-sources, the following kernel configuration options are required and recommended:
For UEFI system you'll also need to enable the following:
In the case you are using BFQ scheduler, it's recommended by BFQ upstream to enable "BFQ hierarchical scheduling support" under "Enable the block layer -> IO Schedulers"
The /run directory
The /run directory is used by systemd and other applications as a non-persistent storage for runtime data like pid files, sockets and state files.
The systemd package will create /run directory itself. However, please note that this change will trigger automatic mounting of it in OpenRC as well, and may trigger using it by different software packages.
Upstream only supports /etc/mtab file being a symlink to /proc/self/mounts. Also not creating this symlink will cause problems with mount (bug #434090) and df (bug #477240). In the past some utilities wrote information (like mount options) into /etc/mtab and thus it was supposed to be file. Currently all software (but nfs bug #487962) is supposed to avoid this problem but before you do switch check bug #477498 to be sure that you are not affected by any regressions.
To create the symlink, run:
Ensure /usr is present at boot time
Using LVM2 and Initramfs
Please remember to append the --udev option even when creating an initramfs without using lvm to prevent errors related with lvmcreate and other problems.
- Install sys-apps/dbus with USE="-systemd". This is probably already done if you have a working desktop environment.
- Enable the systemd USE flag globally (make.conf) and install sys-apps/systemd. This may also be accomplished by a world update. The consolekit use flag should also be disabled to prevent conflicts with the systemd-logind service. You can also switch to a systemd subprofile to use saner USE flags defaults not needing to change make.conf:
Booting with systemd
In order to run systemd, you have to switch the init that your executable kernel (or your initramfs) uses.
Grub Legacy (0.x)
The init=/usr/lib/systemd/systemd argument should be added to the kernel command-line. An example excerpt from grub.conf would look like:
Should the system boot using openrc, try using real_init instead of init
If using the grub2-mkconfig configuration generator, add the init option to GRUB_CMDLINE_LINUX.
If writing a configuration by hand (experts only), append the init parameter to the linux or linux16 command.
In kernel config
You can also set this in your kernel configuration. See "Processor type and features" -> "Built-in kernel command line". Note that this technique works for both grub and grub2.
Post Installation Configuration
systemd supports a few system configuration files to set the most basic system details. If you decide to set this configurations before rebooting using systemd, you will need to launch the following for being able to use some of the referred tools:
A tool called hostnamectl exists for editing /etc/hostname and /etc/machine-info. To change hostname, run:
Refer to man hostnamectl for more options.
Usually, you will get your locale properly migrated from openRC when installing systemd. If you still want to configure it, the tool localectl is used to set locale and console or X11 keymaps. To change the system locale, run the following command.
To change the virtual console keymap:
And finaly, to set the X11 layout:
If needed you can specify the model, variant and options too:
Time & Date
Time and date can be set using the timedatectl utility.
Automatic module loading
Automatic module loading is configured in a different file, or rather directory of files. The configuration files are stored in /etc/modules-load.d. On boot every file with a list of modules will be loaded. The file format is a list of modules seperated by newline and can have any name you want as long as it ends with .conf. You can separate out the module loading by program, service or whatever way you like. My virtualbox.conf example is listed below. But I can image one also has an iptables.conf for all the kernel modules needed for your firewall or one big file with all modules.
Handling of log files
Systemd has its own way of handling log files without needing to rely on any external log system (like syslog-ng or rsyslog). Anyway, you can still configure it to use your preferred external tool for handling them. Please type man journald.conf for learning about how to configure journald to suit your needs.
/tmp is now in tmpfs
Unless you explicitly mount some other filesystem to /tmp in your fstab, systemd will mount /tmp as tmpfs. That means it will be emptied on every boot and its size will be limited to 50% of your RAM size. To know why this is the desired behavior and how to modify it, take a look to API File Systems
Configure verbosity of boot process
When migrating to systemd you will probably notice differences regarding verbosity of boot process:
- quiet option not only affects to kernel output, but also to systemd itself. Then, while you are setting up systemd for your machine, you will probably want to drop it to see any errors could arise more easily. After that, you can add it back to get a quiet (and faster) boot.
- Even passing quiet option, you can still configure systemd to show its status by also passing systemd.show_status=1.
- When not using quiet option, you could get some messages overwriting consoles, that is caused by kernel configuration (see man 5 proc and look for /proc/sys/kernel/printk). To tweak it you can pass the loglevel=5 boot parameter to the kernel (or a lower value like 1).
At some point you will have to reboot your system in order to get systemd running (in system mode). Be sure to read all of this document to ensure you have systemd configured as completely as possible before rebooting. Note that journalctl(8) works with systemd(8) not running, but that systemctl(8) will not do anything useful without systemd running. You will likely want to complete the service configuration (enabling and starting of services) after you get logged in to your system running systemd.
Although systemd originally intended to support running old init.d scripts, that support is not suited well for a dependency-based RC like OpenRC and thus is completely disabled on Gentoo. OpenRC provides additional measures to ensure that init.d scripts can't be run when OpenRC was not used to boot the system (otherwise the results would be unpredictable).
Listing available services
All global service files are installed in /usr/lib/systemd/system. Thus, the simplest way of looking up available service units is listing that directory:
The following file suffixes are of interest:
- .service - plain service files (e.g. ones just running a daemon directly),
- .socket - socket listeners (much like inetd),
- .path - filesystem triggers for services (running services when files change etc.).
Alternatively, systemctl tool can be used to list all services (including implicit ones):
And finally the systemadm graphical tool can be used. It can be installed with the sys-apps/systemd-ui package.
Installing custom service files
Any custom service files should be copied to the /etc/systemd/system directory. The /usr/lib/systemd/system directory is reserved for service files installed by ebuilds.
Enabling and disabling services
The usual way of enabling a service is using
Services can be disabled likewise:
These commands enable services using their default name in default target (both specified in Install section of the service file). However, sometimes services either don't provide that information or you want to use another name/target.
Enabling a service under a custom name
This is especially a case for template services -- services in which part of the name following @ (at sign) is used as a parameter to the service. This is often used to specify the terminal on which getty will run.
To enable a service under custom name, you have to create a symlink to the service file in correct /etc/systemd/system/*.wants directory. The name of that directory can either specify a target or another service which will depend on the new one.
For example, to enable stand-alone wpa_supplicant on wlan0, type:
To disable the service, just remove the symlink:
Some of Gentoo packages already install systemd unit files. For these services, it is enough to enable them. A quick summary of packages installing unit files can be seen on systemd eclass users list.
The following table lists systemd services matching OpenRC ones:
|Gentoo package||OpenRC service||systemd unit||Notes|
|sys-apps/openrc||bootmisc||systemd-tmpfiles-setup.service||always enabled, uses tmpfiles.d|
|consolefont||systemd-vconsole-setup.service||always enabled, uses vconsole.conf|
|fsck||fsck*.service||pulled in implicitly by mounts|
|functions.sh||See note||bug #373219|
|keymaps||systemd-vconsole-setup.service||always enabled, uses vconsole.conf|
|localmount||local-fs.target||actual units are created implicitly from fstab|
|modules||systemd-modules-load.service||always enabled, uses /etc/modules-load.d/*.conf|
|net.*||netctl@.service||net-misc/netctl is originally an Arch Linux tool.|
|NetworkManager.service|| For <networkmanager-0.9.8.4 : enable NetworkManager-dispatcher.service for dispatcher.d scripts to work. |
Enable NetworkManager-wait-online.service to detect that the system has a working internet connection.
|dhcpcd.service||Provided by net-misc/dhcpcd|
|swap||swap.target||actual units are created implicitly from fstab|
|sysctl||systemd-sysctl.service||sysctl.conf and sysctl.d/|
|termencoding||systemd-vconsole-setup.service||always enabled, uses vconsole.conf|
|media-sound/alsa-utils||alsasound||alsa-store.service||(enabled by default)|
|alsa-restore.socket||(enabled by default)|
|net-misc/openntpd||ntpd||ntpd.service||(enabled by default)|
|net-misc/openssh||sshd||sshd.service||runs sshd as a daemon|
|sshd.socket||runs sshd on a inetd-like basis (for each incoming connection)|
|net-misc/wpa_supplicant||wpa-supplicant||wpa_supplicant.service||D-Bus controlled daemon (e.g. for NetworkManager)|
|wpa_supplicant@.service||interface-specific wpa_supplicant (used like email@example.com)|
|net-print/cups||cupsd||cups.service||classic on-boot start up service|
|cups.socket||socket and path activation (cups only started on-demand)|
|sys-apps/irqbalance||irqbalance||irqbalance.service||supports daemon mode only|
|sys-apps/microcode-ctl||microcode_ctl||Configure microcode as a module to let it load the microcode itself. Go to "Processor type and features" -> "CPU microcode loading support" and remember to add the option you need depending on you having intel or amd processor.|
|udev-mount||(builtin)||/dev is mounted as tmpfs|
|sys-power/acpid||acpid||acpid.service||Most of its functionality is done by systemd itself, then, maybe you could consider to stop enabling this|
|x11-apps/xdm||(xdm)||xdm.service||OpenRC uses common xdm init.d installed by x11-base/xorg-server. With systemd you will need to enable corresponding unit file for each DM (gdm.service, kdm.service...)|
systemd-logind & pam_systemd
systemd intends to provide an integrated ConsoleKit replacement called logind. Some applications (like NetworkManager and polkit) provide support for it through USE=systemd. Please note that this flag usually disables ConsoleKit support as well and thus packages may stop working as expected if the procedure described below is not fulfilled. If you're having issues with kde-misc/networkmanagement not being able to detect NetworkManager is running, modify your system-auth file to add pam_systemd.
In order to enable session tracking for systemd-logind, you have to enable the pam_systemd PAM module first. This can be done using USE=systemd on sys-auth/pambase.
Except for tracking user logins (like ConsoleKit does), this will cause all user processes to belong to a cgroup. You can add controllers=... to provide additional cgroup controllers (like cpu for CPU load balancing). You can also add kill-session-processes=1 to ensure that all processes spawned by user are killed on logout. For more information, take a look at pam_systemd man page.
As systemd-bootchart attempts to start /sbin/init, you may have to edit its configuration file:
Result is a report in svg located in /run/log/
syslog-ng conflicts with systemd
should be replaced with:in order to use the syslog-ng service in systemd.
Systemd doesn't seem to respect /etc/conf.d/dmcrypt (bug #429966) and, then, you will need to configure it in /etc/crypttab file:
Check for units that failed to start
To check for units that failed to start you can run:
Enable Debug Mode
To get more informations you need to set the following in /etc/systemd/system.conf:
Please remember to edit /etc/e4rat.conf setting 'init' to /usr/lib/systemd/systemd, otherwise it will keep booting openrc.