diff options
| author | Jakob Lell <jakob@jakoblell.com> | 2022-05-01 22:52:39 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-05-05 18:04:54 +0200 |
| commit | 14736ab6ff1744b3750b5b56ce7ecf40f6422e82 (patch) | |
| tree | 2a03a36960928ebfdeab0156cd78653c163f06b0 /man/systemd.exec.xml | |
| parent | journal: Make journal_default_metrics() static (diff) | |
| download | systemd-14736ab6ff1744b3750b5b56ce7ecf40f6422e82.tar.xz systemd-14736ab6ff1744b3750b5b56ce7ecf40f6422e82.zip | |
Amend documentation for LimitNPROC=
Diffstat (limited to '')
| -rw-r--r-- | man/systemd.exec.xml | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index 7fe54169b2..50c5c89703 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -846,6 +846,14 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting> runtime, and are generally more expressive. For example, <varname>MemoryMax=</varname> is a more powerful (and working) replacement for <varname>LimitRSS=</varname>.</para> + <para>Note that <varname>LimitNPROC=</varname> will limit the number of processes from one (real) UID and + not the number of processes started (forked) by the service. Therefore the limit is cumulative for all + processes running under the same UID. Please also note that the <varname>LimitNPROC=</varname> will not be + enforced if the service is running as root (and not dropping privileges). Due to these limitations, + <varname>TasksMax=</varname> (see <citerefentry><refentrytitle>systemd.resource-control</refentrytitle> + <manvolnum>5</manvolnum></citerefentry>) is typically a better choice than <varname>LimitNPROC=</varname>. + </para> + <para>Resource limits not configured explicitly for a unit default to the value configured in the various <varname>DefaultLimitCPU=</varname>, <varname>DefaultLimitFSIZE=</varname>, … options available in <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>, and – |