diff options
| author | Jakub Wilk <jwilk@jwilk.net> | 2017-09-04 15:25:59 +0200 |
|---|---|---|
| committer | Yu Watanabe <watanabe.yu+github@gmail.com> | 2017-09-04 22:25:59 +0900 |
| commit | ee905de0d60f05c99fb49f71d1c4af2d7e3f3134 (patch) | |
| tree | d7e470a237ca489a5ae081a495cbd8688e2d4c6a /man/systemd.service.xml | |
| parent | c792ec2e3512a672881fc847ff432e26b641c9c9 (diff) | |
man: fix typos (#6739)
Diffstat (limited to 'man/systemd.service.xml')
| -rw-r--r-- | man/systemd.service.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 9863532692..c6fa0edea0 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -330,7 +330,7 @@ <row> <entry><literal>!!</literal></entry> - <entry>This prefix is very similar to <literal>!!</literal>, however it only has an effect on systems lacking support for ambient process capabilities, i.e. without support for <varname>AmbientCapabilities=</varname>. It's intended to be used for unit files that take benefit of ambient capabilities to run processes with minimal privileges wherever possible while remaining compatible with systems that lack ambient capabilities support. Note that when <literal>!!</literal> is used, and a system lacking ambient capability support is detected any configured <varname>SystemCallFilter=</varname> and <varname>CapabilityBoundingSet=</varname> stanzas are implicitly modified, in order to permit spawned processes to drop credentials and capabilites themselves, even if this is configured to not be allowed. Moreover, if this prefix is used and a system lacking ambient capability support is detected <varname>AmbientCapabilities=</varname> will be skipped and not be applied. On systems supporting ambient capabilities, <literal>!!</literal> has no effect and is redundant.</entry> + <entry>This prefix is very similar to <literal>!!</literal>, however it only has an effect on systems lacking support for ambient process capabilities, i.e. without support for <varname>AmbientCapabilities=</varname>. It's intended to be used for unit files that take benefit of ambient capabilities to run processes with minimal privileges wherever possible while remaining compatible with systems that lack ambient capabilities support. Note that when <literal>!!</literal> is used, and a system lacking ambient capability support is detected any configured <varname>SystemCallFilter=</varname> and <varname>CapabilityBoundingSet=</varname> stanzas are implicitly modified, in order to permit spawned processes to drop credentials and capabilities themselves, even if this is configured to not be allowed. Moreover, if this prefix is used and a system lacking ambient capability support is detected <varname>AmbientCapabilities=</varname> will be skipped and not be applied. On systems supporting ambient capabilities, <literal>!!</literal> has no effect and is redundant.</entry> </row> </tbody> </tgroup> @@ -338,7 +338,7 @@ <para><literal>@</literal>, <literal>-</literal>, and one of <literal>+</literal>/<literal>!</literal>/<literal>!!</literal> may be used together and they can appear in any - order. However, only one of <literal>+</literal>, <literal>!</literal>, <literal>!!</literal> may be used a at + order. However, only one of <literal>+</literal>, <literal>!</literal>, <literal>!!</literal> may be used at a time. Note that these prefixes are also supported for the other command line settings, i.e. <varname>ExecStartPre=</varname>, <varname>ExecStartPost=</varname>, <varname>ExecReload</varname>, <varname>ExecStop=</varname> and <varname>ExecStopPost=</varname>.</para> |