This very important commit is very important.
<title>See Also</title>
<para>
<ulink url="https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec">Boot loader specification</ulink>
- <ulink url="https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface">Systemd boot loader interface</ulink>
+ <ulink url="https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface">systemd boot loader interface</ulink>
</para>
</refsect1>
</refentry>
</refsect1>
<refsect1>
- <title>Integration with Systemd</title>
+ <title>Integration with systemd</title>
<refsect2>
- <title>Writing Systemd Unit Files</title>
+ <title>Writing systemd Unit Files</title>
<para>When writing systemd unit files, it is recommended to
consider the following suggestions:</para>
</refsect2>
<refsect2>
- <title>Installing Systemd Service Files</title>
+ <title>Installing systemd Service Files</title>
<para>At the build installation time (e.g. <command>make
install</command> during package build), packages are
convenient.
</para>
- <para>Systemd implicitly loads units as necessary, so just running the <command>status</command> will
+ <para>systemd implicitly loads units as necessary, so just running the <command>status</command> will
attempt to load a file. The command is thus not useful for determining if something was already loaded or
not. The units may possibly also be quickly unloaded after the operation is completed if there's no reason
to keep it in memory thereafter.
<citerefentry project='man-pages'><refentrytitle>sysctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>
parameter <varname>kernel.core_pattern</varname>. The syntax of this parameter is explained in
<citerefentry project='man-pages'><refentrytitle>core</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
- Systemd installs the file <filename>/usr/lib/sysctl.d/50-coredump.conf</filename> which configures
+ systemd installs the file <filename>/usr/lib/sysctl.d/50-coredump.conf</filename> which configures
<varname>kernel.core_pattern</varname> accordingly. This file may be masked or overridden to use a different
setting following normal
<citerefentry><refentrytitle>sysctl.d</refentrytitle><manvolnum>5</manvolnum></citerefentry>
<refnamediv>
<refname>systemd.environment-generator</refname>
- <refpurpose>Systemd environment file generators</refpurpose>
+ <refpurpose>systemd environment file generators</refpurpose>
</refnamediv>
<refsynopsisdiv>
<term><varname>$PATH</varname></term>
<listitem><para>Colon-separated list of directories to use
- when launching executables. Systemd uses a fixed value of
+ when launching executables. systemd uses a fixed value of
<filename>/usr/local/sbin</filename>:<filename>/usr/local/bin</filename>:<filename>/usr/sbin</filename>:<filename>/usr/bin</filename>:<filename>/sbin</filename>:<filename>/bin</filename>.
</para></listitem>
</varlistentry>
<refnamediv>
<refname>systemd.generator</refname>
- <refpurpose>Systemd unit generators</refpurpose>
+ <refpurpose>systemd unit generators</refpurpose>
</refnamediv>
<refsynopsisdiv>
verify that it makes sense, fixing it if possible, and only
failing if it really cannot work.</para>
- <para>Systemd contains native implementations of various tasks
+ <para>systemd contains native implementations of various tasks
that need to be executed as part of the boot process. For example,
it sets the hostname or configures the loopback network device. It
also sets up and mounts various API file systems, such as
r = sd_network_monitor_new(&m->network_monitor, NULL);
if (r == -ENOENT) {
- log_info("Systemd does not appear to be running, not listening for systemd-networkd events.");
+ log_info("systemd does not appear to be running, not listening for systemd-networkd events.");
return 0;
}
if (r < 0)