BUG: pam_cgroup simply doesn't work with cgroup2 about libcgroup HOT 5 CLOSED

The pam module is a great thing to have. Cgrulesengd is a hack anyway.

I think the Slackware community has seen similar problems with cgroupv1 (and had to rely on cgrulesengd), but sometimes people are just too lazy or shy to report bugs :(.

from libcgroup.

Thanks for the bug report, @0n-s.

The pam module hasn't been a priority for the current users of libcgroup, so we have not emphasized development or testing in this area. I'm uncertain how much the libcgroup/pam module is being used, as this is the first issue reported against it even though v2.0 has been out 7+ month. Hmmmm....

from libcgroup.

I'm going to assign this to v2.0.1. I'm not certain if it will be fixed in that release, but I would like us to make a decision on how to proceed with pam by that release.

Thanks again for the report!

from libcgroup.

The pam module is a great thing to have. Cgrulesengd is a hack anyway.

Won't argue with the cgrules comment :)

I think the Slackware community has seen similar problems with cgroupv1 (and had to rely on cgrulesengd), but sometimes people are just too lazy or shy to report bugs :(.

That's good to know. Thank you.

from libcgroup.

Thanks for the comments, @0n-s and @lockywolf. I have merged a fix into main and release-2.0. Let me know if you have any issues.

I'm hoping to get out another release of the 2.0 branch in the next month or so. This fix will obviously be in it.

Thanks again!

from libcgroup.