From: Zbigniew Jędrzejewski-Szmek Date: Sat, 24 May 2014 22:02:16 +0000 (-0400) Subject: man: reword StartupCPUShares= description X-Git-Tag: v213~21 X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=commitdiff_plain;h=b9acccb3c9795c88f1eca003480035917ff3c896 man: reword StartupCPUShares= description Now that we have two options described in the same paragraph, we cannot use singular anymore. --- diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml index e0e49db7d..e91c260bf 100644 --- a/man/systemd.resource-control.xml +++ b/man/systemd.resource-control.xml @@ -119,22 +119,24 @@ along with systemd; If not, see . Assign the specified CPU time share weight to the - processes executed. Takes an integer value. This controls - the cpu.shares control group attribute, - which defaults to 1024. For details about this control group - attribute, see cpu.shares control group + attribute, which defaults to 1024. For details about this + control group attribute, see sched-design-CFS.txt. - The available CPU time is split up among all units within one - slice relative to their CPU time share weight. + 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, - CPUShares= applies to the later runtime - of the system, and if the former is not set also to the - startup phase. This allows priorizing specific services at - boot-up differently than during runtime. - - Implies CPUAccounting=true. + CPUShares= applies to normal runtime of + the system, and if the former is not set also to the startup + phase. Using StartupCPUShares= allows + priorizing specific services at boot-up differently than + during normal runtime. + + Those options imply + CPUAccounting=true.