F15 Feature - convert as many service init files as possible to the native SystemD services

Lennart Poettering mzerqung at 0pointer.de
Wed Nov 24 01:09:01 UTC 2010

On Sun, 21.11.10 00:46, Michał Piotrowski (mkkp4x4 at gmail.com) wrote:

> Hi,
> I would like to help with scripts conversion. IMO the conversion
> action should be coordinated.
> Comments, thoughts?

I would certainly welcome any work in this direction!

I think it would make sense to use Johann's page in the wiki as the
central place to keep track of this:


In another mail on this thread there was already a list of documentation
posted. If you need real-life examples how this should look like, then
consider having a look on a packge such as bluez (keep however in mind
that this package predates the packaging daft, so if in doubt the draft
is right and the package is wrong... ;-)).

Also note that ideally services that currently are exclusively bus
activated gain native systemd files as well, so that they for the first
time can be controlled, supervised and introspected like any other
service on the system.

This adds the following packages to the list of packages to convert:

abrt accountsservice ailurus avahi blueman bluez ConsoleKit
cups-pk-helper dconf fprintd GConf2 gnome-applets gnome-lirc-properties
gnome-settings-daemon gnome-system-monitor gypsy hal kdebase-runtime
kdebase-workspace ModemManager NetworkManager PackageKit polkit rtkit
sectool setroubleshoot system-config-firewall system-config-kdump
system-config-samba system-config-services systemd udisks upower

(A number of these are already converted actually)

If you have any questions regarding writing service files, refer to the
linked documentation, especially the packaging draft:


(Note that this is still a draft, and not official, so take it with a
pinch of salt!)

Also, have a look into the already converted service files in
/lib/systemd/system/*. Note however that service files for stuff
involved in early boot and late shutdown are not suitable as an example,
since they are very different than the service files of normal services,
since early boot/late shutdown services have manually configured
dependencies. You can easily recognize them by the
DefaultDependencies=no setting. Don't be confused by those, just ignore

Of course, the helpful folks on #systemd on freenode will be happy to
answer any questions you might have, and especially I myself will be
(mezcalero). However, for the next weeks I'll be backpacking through
India and not be particularly responsive.


Lennart Poettering - Red Hat, Inc.

More information about the devel mailing list