From Fedora Project Wiki

< Features

Revision as of 14:03, 14 June 2010 by Sundaram (talk | contribs)

systemd System and Session Manager


systemd is a replacement for SysVinit that acts as a system and session manager.


  • Name: [User:Lennart Lennart Poettering]
  • Email: lpoetter AT redhat DOT com

Current status

  • Targeted release: Fedora 14
  • Last updated: 2010-06-01
  • Percentage of completion: 10%

Detailed Description

  • Systemd is currently in Rawhide. The plan is to test it thoroughly and make it the default for Fedora 14, replacing the current default, upstart. Lennart has a few patches for some of the default software, replacing sysvinit daemons with native systemd service files. Rest of the software can continue to include the sysvinit daemons and systemd is compatible with them. Other than some of the default software, we do not recommend users to convert to using systemd services yet for this release.

Benefit to Fedora

Fedora currently uses Upstart but in SysV compatibility mode. systemd is a overall better design as detailed in We hope to reap the benefits of it by leading in distribution integration and including it by default.


Requires building packages for systemd (DONE: ), 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

  1. Boot the system, make sure all services come up.
  2. Move between runlevels, ensure the proper starts and stops take place.
  3. Check the various admin tools such as /sbin/service, system-config-services, chkconfig, etc.

User Experience

The user should notice considerably faster bootup.


Contingency Plan

  • Continue to ship the current Upstart package


Release Notes

Fedora 14 has replaced Upstart with systemd. systemd uses services files located in path/to/files. 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.