FS#52081 - Adding pam_limits.so to systemd PAM fragment
Attached to Project:
Arch Linux
Opened by David Runge (dvzrv) - Thursday, 08 December 2016, 12:00 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 08 December 2016, 13:12 GMT
Opened by David Runge (dvzrv) - Thursday, 08 December 2016, 12:00 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 08 December 2016, 13:12 GMT
|
Details
Description:
Since systemd 232 there is no invocation of pam_limits.so anymore, which renders all settings in /etc/security/limits.conf (/etc/security/limits.d/*) useless. This needs to be added to /etc/pam.d/systemd-user, as mentioned in the upstream NEWS. A simple adding of pam_limits.so fixes this issue (patch attached). Additional info: * systemd NEWS: https://github.com/systemd/systemd/blob/master/NEWS#L303 * bug related to realtime in user services: https://github.com/systemd/systemd/issues/4851 * systemd >= 232 Steps to reproduce: Start user service with settings for realtime scheduling. The PAM settings will not be honored, the user (even if in correct group will not be able to set realtime scheduler for the service). |
This task depends upon
Closed by Dave Reisner (falconindy)
Thursday, 08 December 2016, 13:12 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#52039
Thursday, 08 December 2016, 13:12 GMT
Reason for closing: Duplicate
Additional comments about closing:
Comment by David Runge (dvzrv) -
Thursday, 08 December 2016, 12:01 GMT
Comment by
Dave Reisner (falconindy) -
Thursday, 08 December 2016, 13:11 GMT
patch for adding pam_limits.so to /etc/pam.d/systemd-user
If you're filing this against 232-4, then please upgrade to 232-6.