https://bugs.kde.org/show_bug.cgi?id=433013
andreas.sturmlech...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|New System Monitor in 5.21 |New System Monitor in 5.21
|crashes on startup in |without systemd crashes on
|KSysGuard::CGroupDataModel: |startup in
|:update() |KSysGuard::CGroupDataModel:
| |:update()
URL| |https://github.com/elogind/
| |elogind#differences-relativ
| |e-to-systemd
Platform|Compiled Sources |Gentoo Packages
--- Comment #3 from andreas.sturmlech...@gmail.com ---
> Unlike systemd, whose logind arranges to manage resources for user sessions
> via
> RPC calls to systemd, in elogind there is no systemd so there is no global
> cgroup-based resource management. This has a few implications:
>
> - Elogind does not create "slices" for users. Elogind will not record that
> users are associated with slices.
> - The /run/systemd/slices directory will always be empty.
> - Elogind does not have the concept of a "scope", internally, as it's the same
> as a session. Any API that refers to scopes will always return an error
> code.
--
You are receiving this mail because:
You are watching all bug changes.
