shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2025-02-27 13:57:26 +03:00
Code

man: fix typos (#7029)

Browse Source
This commit is contained in:
Jakub Wilk 2017-10-10 21:59:03 +02:00 committed by Zbigniew Jędrzejewski-Szmek
parent fdaf359bce
commit dcfaecc70a
7 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
man/journald.conf.xml
View File

@ -379,7 +379,7 @@
<listitem><para>The maximum line length to permit when converting stream logs into record logs. When a systemd
unit's standard output/error are connected to the journal via a stream socket, the data read is split into
individual log records at newline (<literal>\n</literal>, ASCII 10) and NUL characters. If no such delimiter is
read for the specified number of bytes a hard log record boundary is artifically inserted, breaking up overly
read for the specified number of bytes a hard log record boundary is artificially inserted, breaking up overly
long lines into multiple log records. Selecting overly large values increases the possible memory usage of the
Journal daemon for each stream client, as in the worst case the journal daemon needs to buffer the specified
number of bytes in memory before it can flush a new log record to disk. Also note that permitting overly large

2
man/systemctl.xml
View File

@ -1795,7 +1795,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<command>poweroff</command> otherwise. This command is asynchronous; it will return after the exit
operation is enqueued, without waiting for it to complete.</para>
<para>The service manager will exit with the the specified exit code, if
<para>The service manager will exit with the specified exit code, if
<replaceable>EXIT_CODE</replaceable> is passed.</para>
</listitem>
</varlistentry>

6
man/systemd-journald.service.xml
View File

@ -123,7 +123,7 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
<para>If <filename>systemd-journald.service</filename> is stopped, the stream connections associated with all
services are terminated. Further writes to those streams by the service will result in <constant>EPIPE</constant>
errors. In order to react gracefully in this case it is recommended that programs logging to standard output/error
ignore such errors. If the the <constant>SIGPIPE</constant> UNIX signal handler is not blocked or turned off, such
ignore such errors. If the <constant>SIGPIPE</constant> UNIX signal handler is not blocked or turned off, such
write attempts will also result in such process signals being generated, see
<citerefentry><refentrytitle>signal</refentrytitle><manvolnum>7</manvolnum></citerefentry>. To mitigate this issue,
systemd service manager explicitly turns off the <constant>SIGPIPE</constant> signal for all invoked processes by
@ -145,12 +145,12 @@ systemd-tmpfiles --create --prefix /var/log/journal</programlisting>
transports listed above, which are inherently record based and where the metadata is always associated with the
individual record.</para>
<para>In addition to the the implicit standard output/error logging of services, stream logging is also available
<para>In addition to the implicit standard output/error logging of services, stream logging is also available
via the <citerefentry><refentrytitle>systemd-cat</refentrytitle><manvolnum>1</manvolnum></citerefentry> command
line tool.</para>
<para>Currently, the number of parallel log streams <filename>systemd-journald</filename> will accept is limited to
4096. When this limit is reached further log streams may be established but will receieve
4096. When this limit is reached further log streams may be established but will receive
<constant>EPIPE</constant> right from the beginning.</para>
</refsect1>

14
man/systemd.exec.xml
View File

@ -2392,7 +2392,7 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
<row>
<entry>205</entry>
<entry><constant>EXIT_LIMITS</constant></entry>
<entry>Failed to adjust resoure limits. See <varname>LimitCPU=</varname> and related settings above.</entry>
<entry>Failed to adjust resource limits. See <varname>LimitCPU=</varname> and related settings above.</entry>
</row>
<row>
<entry>206</entry>
@ -2497,7 +2497,7 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
<row>
<entry>227</entry>
<entry><constant>EXIT_NO_NEW_PRIVILEGES</constant></entry>
<entry>Failed to disable new priviliges. See <varname>NoNewPrivileges=yes</varname> above.</entry>
<entry>Failed to disable new privileges. See <varname>NoNewPrivileges=yes</varname> above.</entry>
</row>
<row>
<entry>228</entry>
@ -2512,7 +2512,7 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
<row>
<entry>230</entry>
<entry><constant>EXIT_PERSONALITY</constant></entry>
<entry>Failed to set up a execution domain (personality). See <varname>Personality=</varname> above.</entry>
<entry>Failed to set up an execution domain (personality). See <varname>Personality=</varname> above.</entry>
</row>
<row>
<entry>231</entry>
@ -2547,22 +2547,22 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
<row>
<entry>238</entry>
<entry><constant>EXIT_STATE_DIRECTORY</constant></entry>
<entry>Failed to set up a the unit's state directory. See <varname>StateDirectory=</varname> above.</entry>
<entry>Failed to set up unit's state directory. See <varname>StateDirectory=</varname> above.</entry>
</row>
<row>
<entry>239</entry>
<entry><constant>EXIT_CACHE_DIRECTORY</constant></entry>
<entry>Failed to set up a the unit's cache directory. See <varname>CacheDirectory=</varname> above.</entry>
<entry>Failed to set up unit's cache directory. See <varname>CacheDirectory=</varname> above.</entry>
</row>
<row>
<entry>240</entry>
<entry><constant>EXIT_LOGS_DIRECTORY</constant></entry>
<entry>Failed to set up a the unit's logging directory. See <varname>LogsDirectory=</varname> above.</entry>
<entry>Failed to set up unit's logging directory. See <varname>LogsDirectory=</varname> above.</entry>
</row>
<row>
<entry>241</entry>
<entry><constant>EXIT_CONFIGURATION_DIRECTORY</constant></entry>
<entry>Failed to set up a the unit's configuration directory. See <varname>ConfigurationDirectory=</varname> above.</entry>
<entry>Failed to set up unit's configuration directory. See <varname>ConfigurationDirectory=</varname> above.</entry>
</row>
</tbody>
</tgroup>

2
man/systemd.nspawn.xml
View File

@ -275,7 +275,7 @@
<term><varname>NotifyReady=</varname></term>
<listitem><para>Configures support for notifications from the container's init process. This is equivalent to
the <option>--notify-ready=</option> command line switch, and takes the same paramaters. See
the <option>--notify-ready=</option> command line switch, and takes the same parameters. See
<citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for details
about the specific options supported.</para></listitem>
</varlistentry>

2
man/systemd.resource-control.xml
View File

@ -500,7 +500,7 @@
</varlistentry>
<varlistentry>
<term><varname>IPAddressAllow=<replaceable>ADDDRESS[/PREFIXLENGTH]…</replaceable></varname></term>
<term><varname>IPAddressAllow=<replaceable>ADDRESS[/PREFIXLENGTH]…</replaceable></varname></term>
<term><varname>IPAddressDeny=<replaceable>ADDRESS[/PREFIXLENGTH]…</replaceable></varname></term>
<listitem>

2
man/systemd.unit.xml
View File

@ -295,7 +295,7 @@
<varname>DefaultDependencies=</varname> in each unit types.</para>
<para>For example, target units will complement all configured
dependencies of type type <varname>Wants=</varname> or
dependencies of type <varname>Wants=</varname> or
<varname>Requires=</varname> with dependencies of type
<varname>After=</varname>. See
<citerefentry><refentrytitle>systemd.target</refentrytitle><manvolnum>5</manvolnum></citerefentry>