Bugzilla – Bug 966878
way too low max proc setting
Last modified: 2017-05-18 15:05:50 UTC
==> /sys/fs/cgroup/pids/user.slice/user-$uid.slice/session-1.scope/pids.current <==
==> /sys/fs/cgroup/pids/user.slice/user-$uid.slice/session-1.scope/pids.max <==
==> /sys/fs/cgroup/pids/user.slice/user-$uid.slice/session-2.scope/pids.current <==
==> /sys/fs/cgroup/pids/user.slice/user-$uid.slice/session-2.scope/pids.max <==
session 1: via text console login
session 2: via GDM
seems to be a bit low.
I do not see this behavior on my laptop. the difference is on my workstation I start tmux in the console session before my first login to the X session.
so the X session might inherit limits from the console session.
on the laptop pids.max reports "max".
(In reply to Marcus Rückert from comment #1)
The seems to be not a bug but a configuration problem. Why do you not configure your system for your needs?
I did not configure anything differently between the 2 machines. and according to dimstar the behavior seen on my laptop is the correct behavior.
both are up2date TW installations.
When i am not swamped, I will test what happens if i login to X on my workstation without a console session.
The default value for UserTasksMax in /etc/logind.conf has been bumped to a value > 10000 and this has been done for TW and any distro based on v228 too.
So I think this bug can be closed now.