Features/systemd
From FedoraProject
Contents |
systemd System and Session Manager
Summary
systemd is a replacement for SysVinit and Upstart that acts as a system and session manager.
Owner
- Name: Lennart Poettering ; Rahul Sundaram
- Email: lpoetter AT redhat DOT com ; sundaram AT fedoraproject.org
Current status
- Targeted release: Fedora 15
- Last updated: 2010-10-19
- Percentage of completion: 100%
- Systemd is currently in Rawhide, and the default
- Patches for various packages have been merged upstream and already found there way into F14 (dbus, udev, avahi, rtkit). Socket activation support that would be nice to have is still missing for rsyslog (merged), rpcbind (submitted upstream, partly merged), cups (not submitted yet).
Detailed Description
- What is systemd? To quote the homepage: "systemd is a system and session manager for Linux, compatible with SysV and LSB init scripts. systemd provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux cgroups, supports snapshotting and restoring of the system state, maintains mount and automount points and implements an elaborate transactional dependency-based service control logic. It can work as a drop-in replacement for sysvinit."
- The plan is to test it thoroughly and make it the default for Fedora 15, replacing the current default, upstart. The more daemons we can update to ship native service files the better. The remaining software can continue to include the sysv init scripts and systemd is compatible with them.
- Instead of bash scripts, systemd uses .service files
- systemd sorts all daemons into their own Linux cgroups, which you may explore beneath /cgroup/systemd in the file system hierarchy.
- systemd's focus is about making the best of Linux and using its features as well as possible. systemd is not intended to be portable. This opens up numerous new possibilities.
Benefit to Fedora
Fedora <= 14 uses Upstart in SysV compatibility mode. systemd is a overall better design as detailed in http://0pointer.de/blog/projects/systemd.html. We hope to reap the benefits of it by leading in distribution integration and including it by default.
Note that in the long run systemd will provide quicker boot up, but completing that will take more work, since some additional changes to our early boot-up need to take place such as splitting up rc.sysinit. However the focus of systemd is primarily doing things right, and not exclusively on speed.
Scope
Requires building packages for systemd (DONE: https://bugzilla.redhat.com/show_bug.cgi?id=598299 ), and taking advantage of it in a dozen or so desktop daemons that will benefit from systemd the most at present and make it default for Fedora 14.
Test Plan
- Boot the system, make sure all services come up.
- Shutdown and ensure that everything is shut down properly.
- Check the various admin tools such as systemctl, systemd-cgls, systemadm, ps and so on.
- Verify that all services are properly put in seperate control groups (systemd-cgls is your friend)
- Verify that "systemctl list-units" shows that all units are in a reasonable state after bootup. (i.e. no red color in the output!)
- Play around with "systemd.unit=emergency.target", "systemd.unit=rescue.target", "systemd.unit=multi-user.target" and suchlike on the kernel command like and switching between the targets via "systemctl isolate".
- Try the following kernel command line options:
- systemd.unit=emergency.target (which gives you something very similar to passing init=/bin/sh but with the option to boot the full system from there)
- systemd.unit=rescue.target (similar, but is mostly equivalent to booting into single user mode on sysv)
- systemd.unit=multi-user.target (to boot only non-graphical stuff)
- systemd.unit=graphical.target (to boot the normal graphical stuff, the default)
User Experience
The user should notice a slightly faster bootup, particularly on SSD.
The administrative features of the init system are considerably extended. (for more details see the aforementioned blog post, in particular the "A short list of other features:" part.
Native systemd service configuration files are much easier to understand and configure compared to sysvinit scripts
Dependencies
- Successful Fedora Package review and addition to rawhide: DONE
- systemd upstream currently lacks three features that we need before Fedora 15:
- proper support for selinux (needs policy changes, and we want to move the policy setup in systemd, not in the initrd). DONE: Latest selinux policy update include changes for systemd.
- We need sysv compatible implementations for /bin/reboot, /bin/shutdown and friends. We currently simply use the implementations upstart provides which work fine, but of course are suboptimal as soon as we want to replace upstart completely. DONE
- complete set of man pages (parts are already documented, this is far from complete however). DONE
- The readahead packages need to be adapted for systemd. readahead is currently one of the very few packages using upstart specific features and hence is not activated when booting with systemd. However, due to the more aggressive parallelization, disk access is much more random when systemd is used and hence the effect of readahead considerable. Or to put it the other way round: unless we have readahead systemd won't perform any better than upstart/sysv during bootup on rotating media. On SSD systemd is considerably faster though in every case as readahead is not necessary there. DONE: systemd now includes its own minimal readahead implementation
- A number of daemons should provide native systemd .service files in addition to sysv init scripts. I have service files for almost all standard F14 services ready, which just need to be added to the rpms. (MOSTLY DONE)
- A number of daemons should be patched for socket activation: rsyslog (UPSTREAM MERGED), dbus (DONE), portmap (PENDING), avahi (DONE), cups. These patches exist (and are public) and should have upstreamable quality, but they need to be reviewed and added to the rpms.
- A number of daemons should ship changed bus activation files to hook them up to systemd for activation (single-line change per package)
- Some (small) bugs in other packages need to be fixed: https://bugzilla.redhat.com/show_bug.cgi?id=614245 (DONE) https://bugzilla.redhat.com/show_bug.cgi?id=612789 (DONE) https://bugzilla.redhat.com/show_bug.cgi?id=612728 (DONE) https://bugzilla.redhat.com/show_bug.cgi?id=612712 (DONE)
- Requires Packaging Guidelines telling us how to use systemd unit files and whether to require both SysVinit and systemd scripts or only one of those. WIP: https://fedoraproject.org/wiki/Systemd_Packaging_Draft
Contingency Plan
- Revert back to ship the current Upstart package, and offer systemd just as an alternative.
Documentation
- The package comes with a full set of man pages. http://0pointer.de/public/systemd-man/
- Project homepage has more details at http://www.freedesktop.org/wiki/Software/systemd
- OpenSuSE systemd documentation: http://en.opensuse.org/SDB:Systemd
Release Notes
Fedora 15 has replaced Upstart with systemd. systemd uses services files located in /lib/systemd/system for services, and /etc/systemd/system for configuration. A dozen desktop daemons [list them] have been initially converted to use systemd service files and small number of programs have been patched to take advantage of it. systemd is compatible with legacy SysV init scripts and rest of the migration will happen incrementally over time.
we need to include Systemd howtos such as
- How do I change the default runlevel?
- How do I know the current run level?
- How to power off the machine ?
