FS#54805 - [systemd] User scope breaks with default 'hybrid' hierarchy
Attached to Project:
Arch Linux
Opened by Alif (alive4ever) - Friday, 14 July 2017, 13:52 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 14 July 2017, 20:41 GMT
Opened by Alif (alive4ever) - Friday, 14 July 2017, 13:52 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 14 July 2017, 20:41 GMT
|
Details
Description:
Currently, systemd is compiled using 'hybrid' default hierarchy. This causes user scope units to break. Additional info: * package version(s): 233.75-3 * config and/or log files etc. Steps to reproduce: $ systemctl --version systemd 233 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN default-hierarchy=hybrid With hybrid default hierarchy, user scope cannot be created [1]. $ systemd-run --user --scope tmux Job for run-r23acdbe580484da0a18cc26e940c29b0.scope failed. See "systemctl status run-r23acdbe580484da0a18cc26e940c29b0.scope" and "journalctl -xe" for details. A workaround is to add systemd.legacy_systemd_cgroup_controller=true boot parameter to force systemd to use 'legacy' hierarchy instead of using the hierarchy specified during compile time. I suggest to compile systemd package using 'legacy' cgroup hierarchy until the 'hybrid' or 'unified' cgroup is considered stable. [1] https://bbs.archlinux.org/viewtopic.php?id=227953 |
This task depends upon
According to the release notes[1], hybrid is the recommended default. I am not agreeing or disagreeing, just pointing it out. Note the third bullet point in the RL speak specifically to this FS.
1. https://lists.freedesktop.org/archives/systemd-devel/2017-March/038419.html