to be used as drop-in files.
* systemd and logind now handle system sleep states, in
- particulary suspending and hibernating.
+ particular suspending and hibernating.
* logind now implements a sleep/shutdown/idle inhibiting logic
suitable for a variety of uses. Soonishly Lennart will blog
includes systemd-hostnamed.
Note that D-Bus can link against libsystemd-login.so, which
- results in a cyclic build dependency. To accomodate for this
+ results in a cyclic build dependency. To accommodate for this
please build D-Bus without systemd first, then build systemd,
then rebuild D-Bus with systemd support.
* man: clarify that time-sync.target is not only sysv compat but also useful otherwise. Same for similar targets
-* journalctl should complain if run with uid != 0 and no persistant logs exist
+* journalctl should complain if run with uid != 0 and no persistent logs exist
* .device aliases need to be implemented with the "following" logic, probably.
<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
<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>
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
<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>
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
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
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
<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
<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
(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
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>
<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
<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>
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,
<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>
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
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
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
<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
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
}
if (parse_bytes(l[1], &bytes) < 0 || bytes <= 0) {
- log_error("[%s:%u] Failed to parse block IO bandwith value, ignoring: %s", filename, line, rvalue);
+ log_error("[%s:%u] Failed to parse block IO bandwidth value, ignoring: %s", filename, line, rvalue);
strv_free(l);
return 0;
}
if (pivot_root(".", "oldroot") < 0) {
log_error("pivot failed: %m");
- /* only chroot if pivot root succeded */
+ /* only chroot if pivot root succeeded */
return -errno;
}
/* Ignore this unit when snapshotting */
bool ignore_on_snapshot;
- /* Did the last condition check suceed? */
+ /* Did the last condition check succeed? */
bool condition_result;
bool in_load_queue:1;
* rest of the string. Every machine with memory protection I've seen
* does it on word boundaries, so is OK with this. But VALGRIND will
* still catch it and complain. The masking trick does make the hash
- * noticably faster for short strings (like English words).
+ * noticeably faster for short strings (like English words).
*/
#ifndef VALGRIND
* rest of the string. Every machine with memory protection I've seen
* does it on word boundaries, so is OK with this. But VALGRIND will
* still catch it and complain. The masking trick does make the hash
- * noticably faster for short strings (like English words).
+ * noticeably faster for short strings (like English words).
*/
#ifndef VALGRIND
* rest of the string. Every machine with memory protection I've seen
* does it on word boundaries, so is OK with this. But VALGRIND will
* still catch it and complain. The masking trick does make the hash
- * noticably faster for short strings (like English words).
+ * noticeably faster for short strings (like English words).
*/
#ifndef VALGRIND
return journal_file_next_entry(f, c, cp, direction, ret, offset);
/* If we have a match then we look for the next matching entry
- * wiht an offset at least one step larger */
+ * with an offset at least one step larger */
return next_for_match(j, j->level0, f, direction == DIRECTION_DOWN ? cp+1 : cp-1, direction, ret, offset);
}
assert(m);
assert(remain_until);
- /* Everytime we get a new message we reset out timeout */
+ /* Every time we get a new message we reset out timeout */
*remain_until = now(CLOCK_MONOTONIC) + DEFAULT_EXIT_USEC;
if (dbus_message_is_signal(m, DBUS_INTERFACE_LOCAL, "Disconnected"))
# Avoid that we conflict with shutdown.target, so that we can stay
# until the very end and do not cancel shutdown.target if we should
-# hapen to be activated very late.
+# happen to be activated very late.
DefaultDependencies=no
~ianmdlvl / elogind.git / commitdiff