From ArchWiki
Jump to navigation Jump to search


"/etc/security/limits.conf does not work if systemd exists". Huh? So why is this page even here, then? For that matter, why does the file itself still exist in Arch? --Chowbok (talk) 09:50, 4 December 2018 (UTC)

The file exists because it's part of the pam package and is still included upstream. Also, I haven't tested this as I adjusted my systemd config but I'm hearing from others that at some point systemd started reading this file, so if your settings in /etc/systemd are commented out it may still work. Would probably be good for someone to confirm this before they delete this page. Vash63 (talk) 15:38, 13 January 2019 (UTC)
Systemd still ignores the file, but pam_limits (enabled by default) will apply it to login sessions. So it is still in effect for normal users, but not for systemd services. Wuestengecko (talk) 16:40, 15 January 2019 (UTC)
Thanks for pointing that out. This Fedora bug confirms your clarification. I updated the article accordingly. Closing this. --Larivact (talk) 17:17, 15 January 2019 (UTC)

Including systemd issues

I think we should discuss setting limits via limits.conf and through systemd files on the same page, since it's basically the same issue. That would mean renaming this page, however, since it wouldn't be limited (ha ha) to the limits.conf file. Any objection to just calling this page "System limits" and including systemd settings on this page as well? Chowbok (talk) 00:16, 6 August 2019 (UTC)

Can you sandbox this first? ⟨Sweyn78⟩ 04:38, 6 August 2019 (UTC)