Commit 96d4ce01 authored by Michael Biebl's avatar Michael Biebl Committed by Lennart Poettering

man: Fix small typo: s/seperate/separate/

parent f10814d9
......@@ -59,7 +59,7 @@
<para><command>runlevel</command> prints the previous
and current SysV runlevel if they are known.</para>
<para>The two runlevel characters are seperated by a
<para>The two runlevel characters are separated by a
single space character. If a runlevel cannot be
determined, N is printed instead. If neither can be
determined, the word "unknown" is printed.</para>
......
......@@ -87,7 +87,7 @@
processes.</para>
<para>The <parameter>state</parameter> parameter
should contain an newline-seperated list of variable
should contain an newline-separated list of variable
assignments, similar in style to an environment
block. A trailing newline is implied if none is
specified. The string may contain any kind of variable
......
......@@ -445,7 +445,7 @@
does not have the effect that any of
the units enabled are also started at
the same time. If this is desired a
seperate <command>start</command>
separate <command>start</command>
command must be invoked for the
unit.</para>
......
......@@ -96,7 +96,7 @@
<listitem><para>Configures the initial
CPU affinity for the init
process. Takes a space-seperated list
process. Takes a space-separated list
of CPU indexes.</para></listitem>
</varlistentry>
</variablelist>
......
......@@ -122,7 +122,7 @@
<listitem><para>Sets the supplementary
Unix groups the processes are executed
as. This takes a space seperated list
as. This takes a space separated list
of group names or IDs. This option may
be specified more than once in which
case all listed groups are set as
......@@ -234,7 +234,7 @@
<listitem><para>Controls the CPU
affinity of the executed
processes. Takes a space-seperated
processes. Takes a space-separated
list of CPU indexes. See
<citerefentry><refentrytitle>sched_setaffinity</refentrytitle><manvolnum>2</manvolnum></citerefentry>
for details.</para></listitem>
......@@ -256,7 +256,7 @@
<listitem><para>Sets environment
variables for executed
processes. Takes a space-seperated
processes. Takes a space-separated
list of variable assignments. This
option may be specified more than once
in which case all listed variables
......@@ -272,7 +272,7 @@
<varname>Environment=</varname> but
reads the environment variables from a
text file. The text file should
contain new-line seperated variable
contain new-line separated variable
assignments. Empty lines and lines
starting with ; or # will be ignored,
which may be used for
......@@ -618,7 +618,7 @@
<listitem><para>Controls the control
groups the executed processes shall be
made members of. Takes a
space-seperated list of cgroup
space-separated list of cgroup
identifiers. A cgroup identifier has a
format like
<filename>cpu:/foo/bar</filename>,
......@@ -637,7 +637,7 @@
arbitrary hierachies -- which can be
configured externally with additional execution limits. By default
systemd will place all executed
processes in seperate per-unit control
processes in separate per-unit control
groups (named after the unit) in the
systemd named hierarchy. Since every
process can be in one group per
......@@ -660,7 +660,7 @@
to limit access a process might have
to the main file-system
hierarchy. Each setting takes a
space-seperated list of absolute
space-separated list of absolute
directory paths. Directories listed in
<varname>ReadWriteDirectories=</varname>
are accessible from within the
......@@ -677,7 +677,7 @@
restricting access with these options
does not extend to submounts of a
directory. You must list submounts
seperately in these setttings to
separately in these setttings to
ensure the same limited access. These
options may be specified more than
once in which case all directories
......
......@@ -180,7 +180,7 @@
<listitem><para>Mount options to use
when mounting. This takes a comma
seperated list of options. This
separated list of options. This
setting is optional.</para></listitem>
</varlistentry>
......
......@@ -290,7 +290,7 @@
by the string value of the environment
variable of the same name. Also
<literal>$FOO</literal> may appear as
seperate word on the command line in
separate word on the command line in
which case the variable is replaced by
its value split at
whitespaces.</para></listitem>
......@@ -306,7 +306,7 @@
command lines may be concatenated in a
single directive, by seperating them
by semicolons (these semicolons must
be passed as seperate words). In that
be passed as separate words). In that
case, the commands are executed one
after the other,
serially. Alternatively, these
......
......@@ -58,7 +58,7 @@ struct init_request_bsd {
/*
* Because of legacy interfaces, "runlevel" and "sleeptime"
* aren't in a seperate struct in the union.
* aren't in a separate struct in the union.
*
* The weird sizes are because init expects the whole
* struct to be 384 bytes.
......
......@@ -514,7 +514,7 @@ static int process_event(Server *s, struct epoll_event *ev) {
/* Yes, this is a bit ugly, we assume that that valid pointers
* are > SD_LISTEN_FDS_START+SERVER_FD_MAX. Which is certainly
* true on Linux (and probably most other OSes, too, since the
* first 4k usually are part of a seperate null pointer
* first 4k usually are part of a separate null pointer
* dereference page. */
if (PTR_TO_INT(ev->data.ptr) >= SD_LISTEN_FDS_START &&
......
......@@ -171,7 +171,7 @@ int sd_is_socket_unix(int fd, int type, int listening, const char *path, size_t
/*
Informs systemd about changed daemon state. This takes a number of
newline seperated environment-style variable assignments in a
newline separated environment-style variable assignments in a
string. The following variables are known:
READY=1 Tells systemd that daemon startup is finished (only
......
......@@ -50,7 +50,7 @@ int main(int argc, char*argv[]) {
/* Verify that merged entries can be
* merged with the same entries they
* can be merged with seperately */
* can be merged with separately */
assert(!job_type_is_mergeable(a, c) || job_type_is_mergeable(d, c));
assert(!job_type_is_mergeable(b, c) || job_type_is_mergeable(d, c));
......
......@@ -338,7 +338,7 @@ struct UnitVTable {
void (*shutdown)(Manager *m);
/* When sending out PropertiesChanged signal, which properties
* shall be invalidated? This is a NUL seperated list of
* shall be invalidated? This is a NUL separated list of
* strings, to minimize relocations a little. */
const char *bus_invalidating_properties;
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment