summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
Diffstat (limited to 'man')
-rw-r--r--man/bootup.xml2
-rw-r--r--man/journalctl.xml8
-rw-r--r--man/journald.conf.xml4
-rw-r--r--man/sd_journal_open.xml2
-rw-r--r--man/sd_journal_print.xml2
-rw-r--r--man/sd_journal_seek_head.xml10
-rw-r--r--man/sd_seat_get_active.xml2
-rw-r--r--man/systemctl.xml6
-rw-r--r--man/systemd-delta.xml2
-rw-r--r--man/systemd-inhibit.xml2
-rw-r--r--man/systemd-readahead-replay.service.xml2
-rw-r--r--man/systemd.conf.xml2
-rw-r--r--man/systemd.exec.xml10
13 files changed, 27 insertions, 27 deletions
diff --git a/man/bootup.xml b/man/bootup.xml
index ed72acfda9..760a5a4c29 100644
--- a/man/bootup.xml
+++ b/man/bootup.xml
@@ -53,7 +53,7 @@
<para>A number of different components are involved in the
system boot. Immediately after power-up, the system
BIOS will do minimal hardware initialization, and hand
- control over to a boot loader stored on a persistant
+ control over to a boot loader stored on a persistent
storage device. This boot loader will then invoke an
OS kernel from disk (or the network). In the Linux
case this kernel now (optionally) extracts and
diff --git a/man/journalctl.xml b/man/journalctl.xml
index f314fb6d26..05c8703d28 100644
--- a/man/journalctl.xml
+++ b/man/journalctl.xml
@@ -141,7 +141,7 @@
<term><option>-f</option></term>
<listitem><para>Show only most recent
- journal entries, and continously print
+ journal entries, and continuously print
new entries as they are appended to
the journal.</para></listitem>
</varlistentry>
@@ -189,9 +189,9 @@
is very similar but shows monotonic
timestamps instead of wallclock
timestamps. <literal>verbose</literal>
- shows the full structered entry items
+ shows the full structured entry items
with all
- fiels. <literal>export</literal>
+ fields. <literal>export</literal>
serializes the journal into a binary
(but mostly text-based) stream
suitable for backups and network
@@ -209,7 +209,7 @@
<term><option>-q</option></term>
<listitem><para>Suppresses any warning
- message regarding inaccessable system
+ message regarding inaccessible system
journals when run as normal
user.</para></listitem>
</varlistentry>
diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index 36227092bb..d7caea83cc 100644
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -174,7 +174,7 @@
influences the granularity in which
disk space is made available through
rotation, i.e. deletion of historic
- data. Defaults to one eigth of the
+ data. Defaults to one eighth of the
values configured with
<varname>SystemMaxUse=</varname> and
<varname>RuntimeMaxUse=</varname>, so
@@ -317,7 +317,7 @@
directory
<filename>/var/log/journal</filename>
is not created if needed, so that its
- existance controls where log data
+ existence controls where log data
goes. <literal>none</literal> turns
off all storage, all log data received
will be dropped. Forwarding to other
diff --git a/man/sd_journal_open.xml b/man/sd_journal_open.xml
index ffd9a2c481..b99c67da46 100644
--- a/man/sd_journal_open.xml
+++ b/man/sd_journal_open.xml
@@ -92,7 +92,7 @@
only journal files generated on the local machine will
be opened. <literal>SD_JOURNAL_RUNTIME_ONLY</literal>
makes sure only volatile journal files will be opened,
- excluding those which are stored on persistant
+ excluding those which are stored on persistent
storage. <literal>SD_JOURNAL_SYSTEM_ONLY</literal>
will ensure that only journal files of system services
and the kernel (in opposition to user session processes) will
diff --git a/man/sd_journal_print.xml b/man/sd_journal_print.xml
index 05c1ebea77..dfe99192e7 100644
--- a/man/sd_journal_print.xml
+++ b/man/sd_journal_print.xml
@@ -172,7 +172,7 @@ sd_journal_send("MESSAGE=Hello World, this is PID %lu!", (unsigned long) getpid(
<para><citerefentry><refentrytitle>syslog</refentrytitle><manvolnum>3</manvolnum></citerefentry>
and and <function>sd_journal_print()</function> may
- largely be used interchangably
+ largely be used interchangeably
functionality-wise. However, note that log messages
logged via the former take a different path to the
journal server than the later, and hence global
diff --git a/man/sd_journal_seek_head.xml b/man/sd_journal_seek_head.xml
index b6a9a731c1..f8a4eb1d20 100644
--- a/man/sd_journal_seek_head.xml
+++ b/man/sd_journal_seek_head.xml
@@ -92,7 +92,7 @@
<para><function>sd_journal_seek_head()</function>
seeks to the beginning of the journal, i.e. the oldest
- avilable entry.</para>
+ available entry.</para>
<para>Similar,
<function>sd_journal_seek_tail()</function> may be
@@ -110,7 +110,7 @@
(wallclock) timestamp, i.e. CLOCK_REALTIME. Note that
the realtime clock is not necessary monotonic. If a
realtime timestamp is ambiguous it is not defined
- which position is seeked to.</para>
+ which position is sought to.</para>
<para><function>sd_journal_seek_cursor()</function>
seeks to the entry located at the specified cursor
@@ -125,12 +125,12 @@
may be retrieved via
<citerefentry><refentrytitle>sd_journal_get_data</refentrytitle><manvolnum>3</manvolnum></citerefentry>. If
no entry exists that matches exactly the specified
- seek address the next closest is seeked to. If
+ seek address the next closest is sought to. If
<citerefentry><refentrytitle>sd_journal_next</refentrytitle><manvolnum>3</manvolnum></citerefentry>
- is used the closest following entry will be seeked to,
+ is used the closest following entry will be sought to,
if
<citerefentry><refentrytitle>sd_journal_previous</refentrytitle><manvolnum>3</manvolnum></citerefentry>
- is used the closest preceeding entry is seeked
+ is used the closest preceding entry is sought
to.</para>
</refsect1>
diff --git a/man/sd_seat_get_active.xml b/man/sd_seat_get_active.xml
index fa47378577..801c16a4bb 100644
--- a/man/sd_seat_get_active.xml
+++ b/man/sd_seat_get_active.xml
@@ -118,7 +118,7 @@
<para><function>sd_seat_can_multi_session()</function>
may be used to determine whether a specific seat is
capable of multi-session, i.e. allows multiple login
- sessions in parallel (whith only one being active at a
+ sessions in parallel (with only one being active at a
time).</para>
<para><function>sd_seat_can_tty()</function> may be
diff --git a/man/systemctl.xml b/man/systemctl.xml
index bf31b6114d..3c0a7950a0 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -447,7 +447,7 @@
<term><option>-f</option></term>
<listitem><para>When used with
- <command>status</command> continously
+ <command>status</command> continuously
prints new journal entries as they are
appended to the
journal.</para></listitem>
@@ -1202,10 +1202,10 @@
directory, and the path to the new
system manager binary below it to
execute as PID 1. If the latter is
- ommitted or the empty string, a
+ omitted or the empty string, a
systemd binary will automatically be
searched for and used as init. If the
- system manager path is ommitted or
+ system manager path is omitted or
equal the empty string the state of
the initrd's system manager process is
passed to the main system manager,
diff --git a/man/systemd-delta.xml b/man/systemd-delta.xml
index 9ded28be43..4e57d18fcc 100644
--- a/man/systemd-delta.xml
+++ b/man/systemd-delta.xml
@@ -155,7 +155,7 @@
<listitem><para>When showing modified
files, when a file is overridden show a
- diff aswell. This option takes a
+ diff as well. This option takes a
boolean argument.</para></listitem>
</varlistentry>
diff --git a/man/systemd-inhibit.xml b/man/systemd-inhibit.xml
index 81ec9ef9ab..e19892b3f1 100644
--- a/man/systemd-inhibit.xml
+++ b/man/systemd-inhibit.xml
@@ -110,7 +110,7 @@
inhibiting
reboot/power-off/halt/kexec,
suspending/hibernating, resp. the
- automatic idle detection. If ommitted
+ automatic idle detection. If omitted
defaults to
<literal>idle:sleep:shutdown</literal>,
i.e. takes all possible
diff --git a/man/systemd-readahead-replay.service.xml b/man/systemd-readahead-replay.service.xml
index e37b1a9edf..b56fdb8100 100644
--- a/man/systemd-readahead-replay.service.xml
+++ b/man/systemd-readahead-replay.service.xml
@@ -85,7 +85,7 @@
and
<filename>systemd-readahead-replay.service</filename>
are activated at boot so that access patterns from the
- preceeding boot are replayed and new data collected
+ preceding boot are replayed and new data collected
for the subsequent boot. However, on read-only media
where the collected data cannot be stored it might
be a good idea to disable
diff --git a/man/systemd.conf.xml b/man/systemd.conf.xml
index fb038eaf6d..804a50ead6 100644
--- a/man/systemd.conf.xml
+++ b/man/systemd.conf.xml
@@ -125,7 +125,7 @@
hierarchy. By default systemd will
mount all controllers which are
enabled in the kernel in individual
- hierachies, with the exception of
+ hierarchies, with the exception of
those listed in this setting. Takes a
space separated list of comma
separated controller names, in order
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index 8d3b3da22e..eff75d033a 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -931,18 +931,18 @@
<term><varname>BlockIOWriteBandwidth=</varname></term>
<listitem><para>Set the per-device
- overall block IO bandwith limit for
+ overall block IO bandwidth limit for
the executed processes. Takes a space
separated pair of a file path and a
- bandwith value (in bytes per second)
+ bandwidth value (in bytes per second)
to specify the device specific
bandwidth. The file path may be
specified as path to a block device
node or as any other file in which
case the backing block device of the
file system of the file is determined.
- If the bandwith is suffixed with K, M,
- G, or T the specified bandwith is
+ If the bandwidth is suffixed with K, M,
+ G, or T the specified bandwidth is
parsed as Kilobytes, Megabytes,
Gigabytes, resp. Terabytes (Example:
"/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0
@@ -951,7 +951,7 @@
and
<literal>blkio.write_bps_device</literal>
control group attributes. Use this
- option multiple times to set bandwith
+ option multiple times to set bandwidth
limits for multiple devices. For
details about these control group
attributes see <ulink
generated by cgit v1.2.3-54-g00ecf (git 2.45.2) at 2024-11-07 15:54:19 +0000