lol

manual: Clarify that limits.conf doesn't apply to systemd services. (#40267)

Say how systemd services can be set instead.

Sources:

* https://bugzilla.redhat.com/show_bug.cgi?id=754285
* https://ro-che.info/articles/2017-03-26-increase-open-files-limit

Signed-off-by: Niklas Hambüchen <mail@nh2.me>

authored by

Niklas Hambüchen and committed by
xeji
7f79a4fe 0c321443

+9 -2
+4
nixos/modules/security/pam.nix
··· 449 449 <varname>item</varname>, and <varname>value</varname> 450 450 attribute. The syntax and semantics of these attributes 451 451 must be that described in the limits.conf(5) man page. 452 + 453 + Note that these limits do not apply to systemd services, 454 + whose limits can be changed via <option>systemd.extraConfig</option> 455 + instead. 452 456 ''; 453 457 }; 454 458
+5 -2
nixos/modules/system/boot/coredump.nix
··· 15 15 Enables storing core dumps in systemd. 16 16 Note that this alone is not enough to enable core dumps. The maximum 17 17 file size for core dumps must be specified in limits.conf as well. See 18 - <option>security.pam.loginLimits</option> as well as the limits.conf(5) 19 - man page. 18 + <option>security.pam.loginLimits</option> and the limits.conf(5) 19 + man page (these specify the core dump limits for user login sessions) 20 + and <option>systemd.extraConfig</option> (where e.g. 21 + <literal>DefaultLimitCORE=1000000</literal> can be specified to set 22 + the core dump limit for systemd system-level services). 20 23 ''; 21 24 }; 22 25