FS#52081 : Adding pam_limits.so to systemd PAM fragment

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

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

Task Type	Feature Request
Category	Packages: Core
Status	Closed
Assigned To	No-one
Architecture	All
Severity	Medium
Priority	Normal
Reported Version
Due in Version	Undecided
Due Date	Undecided
Percent Complete
Votes	0
Private	No

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~~