Join GitHub today
resource-control doesn't work for user instance #3744
systemd version the issue has been seen with
Archlinux (update: 17/07/2016)
Expected behaviour you didn't see
Unexpected behaviour you saw
Steps to reproduce the problem
With cgroup v1 (not unified hierarchy).
I don't know if it's normal or not.
In case it's not possible, I think it should be mentioned in the systemd.resource-control man page.
Do you need more information ?
referenced this issue
Jul 31, 2016
@LukeShu currently you can't control CPU with cgroup v2
@tchernomax Wow, I'm embarased.
However, I still think this has regressed. But let's test it using a v2 controller that actually exists:
First, let's verify that it works for the system instance:
We can see that it got killed once it allocated tried allocating anything more than
Now, let's try the same thing, but with the user instance:
For fun, go ahead and run
This time, you see it use up the entire system memory before the OOM killer fixes that:
(the journal actually stopped updating during the low-memory situation; htop tells me that it did fill the entire ~3.6G I had free, not just the 2.3G that it logged to the journal.
Which makes sense, because