This changes the default from putting all units into the root slice to placing them into the app slice in the user manager. The advantage is that we get the right behaviour in most cases, and we'll need special case handling in all other cases anyway. Note that we have currently defined that applications *should* start their unit names with app-, so we could also move only these by creating a drop-in for app-.scope and app-.service. However, that would not answer the question on how we should manage session.slice. And we would end up placing anything that does not fit the system (e.g. anything started by dbus-broker currently) into the root slice.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.