picnoir
/
Systemd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

man: spelling fixes

This commit is contained in:
Kay Sievers 2010-06-24 17:25:16 +02:00 committed by Lennart Poettering
parent 771610b04d
commit 436c44a5d6
9 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
man/daemon.xml
View File

@ -65,7 +65,7 @@
starts, it should execute the following steps
as part of the initialization. Note that these
steps are unnecessary for new-style daemons,
and should only be implemented if compatbility
and should only be implemented if compatibility
with SysV is essential.</para>
<orderedlist>
@ -213,7 +213,7 @@
<listitem><para>As much as possible,
rely on systemd's functionality to
limit the accces of the daemon to
limit the access of the daemon to
files, services and other
resources. i.e. rely on systemd's
resource limit control instead of
@ -250,7 +250,7 @@
scheme pointed out below. Like D-Bus
activation this enables on-demand
starting of services as well as it
allows improved parallization of
allows improved parallelization of
service start-up. Also, for state-less
protocols (such as syslog, DNS) a
daemon implementing socket-based

2
man/runlevel.xml
View File

@ -64,7 +64,7 @@
determined N is printed instead. If neither can be
determined the word "unknown" is printed.</para>
<para>Unless overriden in the environment this will
<para>Unless overridden in the environment this will
check the utmp database for recent runlevel
changes.</para>
</refsect1>

2
man/sd_booted.xml
View File

@ -70,7 +70,7 @@
<para>On failure, this call returns a negative
errno-style error code. If the system was booted up
with systemd as init system this call returns a
postive return value, zero otherwise.</para>
positive return value, zero otherwise.</para>
</refsect1>
<refsect1>

2
man/sd_listen_fds.xml
View File

@ -90,7 +90,7 @@
<citerefentry><refentrytitle>sd_is_socket_inet</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sd_is_socket_unix</refentrytitle><manvolnum>3</manvolnum></citerefentry>
are provided. In order to maximize flexibility it is
recommened to make these checks as loose as possible
recommended to make these checks as loose as possible
without allowing incorrect setups. i.e. often the
actual port number a socket is bound to matters little
for the service to work, hence it should not be

2
man/sd_notify.xml
View File

@ -153,7 +153,7 @@
</varlistentry>
</variablelist>
<para>It is recommened to prefix variable names that
<para>It is recommended to prefix variable names that
are not shown in the list above with
<varname>X_</varname> to avoid namespace
clashes.</para>

2
man/systemctl.xml
View File

@ -102,7 +102,7 @@
<term><option>--replace</option></term>
<listitem><para>If the requested
operation conflicts with an exisiting
operation conflicts with an existing
unfinished operation, replace the
existing operation by the requested
operation. If this is not specified

2
man/systemd-install.xml
View File

@ -149,7 +149,7 @@
<listitem><para>Checks whether any of
the units specified are
installed. This will check for the
existance of a number of symlinks as
existence of a number of symlinks as
encoded in the [Install] section of a
unit file.</para></listitem>
</varlistentry>

2
man/systemd.unit.xml
View File

@ -64,7 +64,7 @@
<para>A unit configuration file encodes information
about a service, a socket, a device, a mount point, an
automount point, a swap file or patition, a start-up
automount point, a swap file or partition, a start-up
target, a file system path or a timer controlled and
supervised by <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>. The syntax is inspired by XDG
<filename>.desktop</filename> files, which are in turn

10
man/systemd.xml
View File

@ -137,7 +137,7 @@
<listitem><para>Extract D-Bus
interface introspection data. This is
mostly useful at build ot install time
mostly useful at build at install time
to generate data suitable for the
D-Bus interfaces
repository. Optionally the interface
@ -459,7 +459,7 @@
<term><varname>$SYSTEMD_LOG_LEVEL</varname></term>
<listitem><para>systemd reads the
log level from this environment
variable. This can be overriden with
variable. This can be overridden with
<option>--log-level=</option>.</para></listitem>
</varlistentry>
@ -467,7 +467,7 @@
<term><varname>$SYSTEMD_LOG_TARGET</varname></term>
<listitem><para>systemd reads the
log target from this environment
variable. This can be overriden with
variable. This can be overridden with
<option>--log-target=</option>.</para></listitem>
</varlistentry>
@ -475,7 +475,7 @@
<term><varname>$SYSTEMD_LOG_COLOR</varname></term>
<listitem><para>Controls whether
systemd highlights important log
messages. This can be overriden with
messages. This can be overridden with
<option>--log-color=</option>.</para></listitem>
</varlistentry>
@ -484,7 +484,7 @@
<listitem><para>Controls whether
systemd prints the code location along
with log messages. This can be
overriden with
overridden with
<option>--log-location=</option>.</para></listitem>
</varlistentry>