diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml index ea728dff33..f0b355d46a 100644 --- a/man/systemd.resource-control.xml +++ b/man/systemd.resource-control.xml @@ -189,10 +189,10 @@ Scheduler. The available CPU time is split up among all units within one slice relative to their CPU time weight. A higher weight means more CPU time, a lower weight means less. - While StartupCPUWeight= only applies to the startup phase of the system, + While StartupCPUWeight= applies to the startup and shutdown phases of the system, CPUWeight= applies to normal runtime of the system, and if the former is not set also to - the startup phase. Using StartupCPUWeight= allows prioritizing specific services at - boot-up differently than during normal runtime. + the startup and shutdown phases. Using StartupCPUWeight= allows prioritizing specific services at + boot-up and shutdown differently than during normal runtime. These settings replace CPUShares= and StartupCPUShares=. @@ -247,10 +247,10 @@ of the CPUs will be used by the processes as it may be limited by parent units. The effective configuration is reported as EffectiveCPUs=. - While StartupAllowedCPUs= only applies to the startup phase of the system, + While StartupAllowedCPUs= applies to the startup and shutdown phases of the system, AllowedCPUs= applies to normal runtime of the system, and if the former is not set also to - the startup phase. Using StartupAllowedCPUs= allows prioritizing specific services at - boot-up differently than during normal runtime. + the startup and shutdown phases. Using StartupAllowedCPUs= allows prioritizing specific services at + boot-up and shutdown differently than during normal runtime. This setting is supported only with the unified control group hierarchy. @@ -269,10 +269,10 @@ guarantee that all of the memory NUMA nodes will be used by the processes as it may be limited by parent units. The effective configuration is reported as EffectiveMemoryNodes=. - While StartupAllowedMemoryNodes= only applies to the startup phase of the system, + While StartupAllowedMemoryNodes= applies to the startup and shutdown phases of the system, AllowedMemoryNodes= applies to normal runtime of the system, and if the former is not set also to - the startup phase. Using StartupAllowedMemoryNodes= allows prioritizing specific services at - boot-up differently than during normal runtime. + the startup and shutdown phases. Using StartupAllowedMemoryNodes= allows prioritizing specific services at + boot-up and shutdown differently than during normal runtime. This setting is supported only with the unified control group hierarchy. @@ -458,12 +458,12 @@ relative to their block I/O weight. A higher weight means more I/O bandwidth, a lower weight means less. - While StartupIOWeight= only applies - to the startup phase of the system, + While StartupIOWeight= applies + to the startup and shutdown phases of the system, IOWeight= applies to the later runtime of the system, and if the former is not set also to the startup - phase. This allows prioritizing specific services at boot-up - differently than during runtime. + and shutdown phases. This allows prioritizing specific services at boot-up + and shutdown differently than during runtime. These settings replace BlockIOWeight= and StartupBlockIOWeight= and disable settings prefixed with BlockIO or StartupBlockIO. @@ -1189,10 +1189,10 @@ DeviceAllow=/dev/loop-control The available CPU time is split up among all units within one slice relative to their CPU time share weight. - While StartupCPUShares= only applies to the startup phase of the system, + While StartupCPUShares= applies to the startup and shutdown phases of the system, CPUShares= applies to normal runtime of the system, and if the former is not set also to - the startup phase. Using StartupCPUShares= allows prioritizing specific services at - boot-up differently than during normal runtime. + the startup and shutdown phases. Using StartupCPUShares= allows prioritizing specific services at + boot-up and shutdown differently than during normal runtime. Implies CPUAccounting=yes. @@ -1249,11 +1249,11 @@ DeviceAllow=/dev/loop-control weight. While StartupBlockIOWeight= only - applies to the startup phase of the system, + applies to the startup and shutdown phases of the system, BlockIOWeight= applies to the later runtime of the system, and if the former is not set also to the - startup phase. This allows prioritizing specific services at - boot-up differently than during runtime. + startup and shutdown phases. This allows prioritizing specific services at + boot-up and shutdown differently than during runtime. Implies BlockIOAccounting=yes.