mirror of
https://github.com/systemd/systemd.git
synced 2024-12-22 17:35:35 +03:00
man: Documentation spelling fixes
This commit is contained in:
parent
c98a949fb2
commit
9f7dad774e
@ -795,7 +795,7 @@ AM_CONDITIONAL(HAVE_SYSTEMD, [test -n "$with_systemdsystemunitdir" -a "x$with_sy
|
||||
machines, and optionally allows their
|
||||
installation even on machines lacking
|
||||
systemd. (Modification of this snippet for the
|
||||
user unit directory is left as an excercise for the
|
||||
user unit directory is left as an exercise for the
|
||||
reader.)</para>
|
||||
|
||||
<para>Additionally, to ensure that
|
||||
|
@ -250,7 +250,7 @@
|
||||
cgroup will be created by default for
|
||||
each user logging in, in addition to
|
||||
the cgroup in the named 'name=systemd'
|
||||
hierarchy. If ommited, defaults to an
|
||||
hierarchy. If omitted, defaults to an
|
||||
empty list. This may be used to move
|
||||
user sessions into their own groups in
|
||||
the 'cpu' hierarchy which ensures that
|
||||
@ -267,7 +267,7 @@
|
||||
separated list of cgroup controllers
|
||||
in which hierarchies the logged in
|
||||
processes will be reset to the root
|
||||
cgroup. If ommited, defaults to 'cpu',
|
||||
cgroup. If omitted, defaults to 'cpu',
|
||||
meaning that a 'cpu' cgroup grouping
|
||||
inherited from the login manager will
|
||||
be reset for the processes of the
|
||||
|
@ -386,8 +386,8 @@
|
||||
<term><option>--host</option></term>
|
||||
|
||||
<listitem><para>Execute operation
|
||||
remotely. Specifiy a hostname, or
|
||||
username and hostname seperated by @,
|
||||
remotely. Specify a hostname, or
|
||||
username and hostname separated by @,
|
||||
to connect to. This will use SSH to
|
||||
talk to the remote systemd
|
||||
instance.</para></listitem>
|
||||
|
@ -115,7 +115,7 @@
|
||||
<term><option>--icon=</option></term>
|
||||
|
||||
<listitem><para>Specify an icon name
|
||||
alongside the pasword query, which may
|
||||
alongside the password query, which may
|
||||
be used in all agents supporting
|
||||
graphical display. The icon name
|
||||
should follow the <ulink
|
||||
|
@ -61,7 +61,7 @@
|
||||
container. In many ways it is similar to
|
||||
<citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
||||
but more powerful since it fully virtualizes the file
|
||||
system hierachy, as well as the process tree, the
|
||||
system hierarchy, as well as the process tree, the
|
||||
various IPC subsystems and the host and domain
|
||||
name.</para>
|
||||
|
||||
@ -106,7 +106,7 @@
|
||||
<para>Note that running two
|
||||
<command>systemd-nspawn</command> containers from the
|
||||
same directory tree will not make processes in them
|
||||
see each other. The PID namespace seperation of the
|
||||
see each other. The PID namespace separation of the
|
||||
two containers is complete and the containers will
|
||||
share very few runtime objects except for the
|
||||
underlying file system.</para>
|
||||
|
@ -638,7 +638,7 @@
|
||||
executed process. See
|
||||
<citerefentry><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
||||
for details. Takes a whitespace
|
||||
seperated list of capability names as
|
||||
separated list of capability names as
|
||||
read by
|
||||
<citerefentry><refentrytitle>cap_from_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
|
||||
Capabilities listed will be included
|
||||
@ -715,7 +715,7 @@
|
||||
path for this unit is implied. This
|
||||
option may be used to place executed
|
||||
processes in arbitrary groups in
|
||||
arbitrary hierachies -- which can be
|
||||
arbitrary hierarchies -- which can be
|
||||
configured externally with additional execution limits. By default
|
||||
systemd will place all executed
|
||||
processes in separate per-unit control
|
||||
@ -753,7 +753,7 @@
|
||||
usual file access controls would
|
||||
permit this. Directories listed in
|
||||
<varname>InaccessibleDirectories=</varname>
|
||||
will be made inaccesible for processes
|
||||
will be made inaccessible for processes
|
||||
inside the namespace. Note that
|
||||
restricting access with these options
|
||||
does not extend to submounts of a
|
||||
|
@ -518,7 +518,7 @@
|
||||
<term><varname>Broadcast=</varname></term>
|
||||
<listitem><para>Takes a boolean
|
||||
value. This controls the SO_BROADCAST
|
||||
option, which allows boradcast
|
||||
option, which allows broadcast
|
||||
datagrams to be sent from this
|
||||
socket. Defaults to
|
||||
<option>false</option>.</para></listitem>
|
||||
|
@ -78,7 +78,7 @@
|
||||
|
||||
<para>All swap units automatically get the appropriate
|
||||
dependencies on the devices (resp. on the mount points
|
||||
of the files) they are actived from.</para>
|
||||
of the files) they are activated from.</para>
|
||||
|
||||
<para>Swap units with
|
||||
<varname>DefaultDependencies=</varname> enabled
|
||||
|
@ -610,7 +610,7 @@
|
||||
verify that the specified condition is
|
||||
true. With
|
||||
<varname>ConditionPathExists=</varname>
|
||||
a file existance condition can be
|
||||
a file existence condition can be
|
||||
checked before a unit is started. If
|
||||
the specified absolute path name does
|
||||
not exist startup of a unit will not
|
||||
|
Loading…
Reference in New Issue
Block a user