[systemd-devel] Memory used by service reported wrong

Mantas Mikulėnas grawity at gmail.com
Sun Mar 17 10:08:15 UTC 2019


On Sat, Mar 16, 2019 at 7:58 PM Manuel Reimer <Manuel.Spam at nurfuerspam.de>
wrote:

> I've found my processes:
>
> # systemctl status session-8.scope
> ● session-8.scope - Session 8 of user kodi
>     Loaded: loaded (/run/systemd/transient/session-8.scope; transient)
> Transient: yes
>     Active: active (running) since Sat 2019-03-16 18:55:16 CET; 2min 1s ago
>      Tasks: 33
>     Memory: 198.3M
>     CGroup: /user.slice/user-420.slice/session-8.scope
>             ├─1109 /usr/bin/xinit /usr/bin/dbus-launch
> --exit-with-session /usr/>
>             ├─1111 (sd-pam)
>             ├─1112 /usr/lib/Xorg :0 -nolisten tcp vt7 :0
>             ├─1117 /bin/sh /usr/bin/kodi-standalone
>             ├─1120 /usr/bin/dbus-launch --exit-with-session
> /usr/bin/kodi-standa>
>             ├─1121 /usr/bin/dbus-daemon --syslog --fork --print-pid 4
> --print-ad>
>             ├─1125 /bin/sh /usr/bin/kodi --standalone
>             └─1133 /usr/lib/kodi/kodi-x11 --standalone
>

Looks like Kodi startup creates a systemd-logind session for itself, which
makes sense, as it seems to work practically the same as any other
interactive X11 session; by doing so it gets device access and polkit
access.


>
> Mar 16 18:55:16 manuelsvdr systemd[1]: Started Session 8 of user kodi.
>
> This scope does not have my memory limitation enabled. How to get this
> setting in there?
>
>
Configure the limits in user-420.slice.d/ instead.

-- 
Mantas Mikulėnas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20190317/1538833b/attachment.html>


More information about the systemd-devel mailing list