diff options
Diffstat (limited to 'chapter09/systemd-custom.xml')
| -rw-r--r-- | chapter09/systemd-custom.xml | 33 |
1 files changed, 17 insertions, 16 deletions
diff --git a/chapter09/systemd-custom.xml b/chapter09/systemd-custom.xml index 787fd4572..809c1a273 100644 --- a/chapter09/systemd-custom.xml +++ b/chapter09/systemd-custom.xml @@ -49,13 +49,14 @@ EOF</userinput></screen> <title>Disabling tmpfs for /tmp</title> <para>By default, <filename class="directory">/tmp</filename> is created as - a tmpfs. If this is not desired, it can be overridden by the following:</para> + a tmpfs. If this is not desired, it can be overridden by executing the + following command:</para> <screen role="nodump"><userinput>ln -sfv /dev/null /etc/systemd/system/tmp.mount</userinput></screen> <para>Alternatively, if a a separate partition for <filename class="directory">/tmp</filename> is desired, specify that - partition in an <filename>/etc/fstab</filename> entry.</para> + partition in a <filename>/etc/fstab</filename> entry.</para> <warning> <para> @@ -87,7 +88,7 @@ EOF</userinput></screen> <filename class="directory">/etc/tmpfiles.d</filename> override files with the same name in <filename class="directory">/usr/lib/tmpfiles.d</filename>. See - <filename>tmpfiles.d(5)</filename> manual page for file format + <filename>tmpfiles.d(5)</filename> manual page for file format details.</para> <para> @@ -103,7 +104,7 @@ EOF</userinput></screen> is really only applicable to btrfs filesystems. It references type v which in turn references type d (directory). This then creates the specified directory if is is not present and adjusts the permissions - and ownership as specified. Contents of the directory will be + and ownership as specified. Contents of the directory will be subject to time based cleanup if the age argument is specified. </para> @@ -121,7 +122,7 @@ cp /usr/lib/tmpfiles.d/tmp.conf /etc/tmpfiles.d</userinput></screen> <sect2> <title>Overriding Default Services Behavior</title> - <para>The parameter of a unit can be overriden by creating a directory + <para>The parameters of a unit can be overriden by creating a directory and a configuration file in <filename class="directory">/etc/systemd/system</filename>. For example:</para> @@ -180,7 +181,7 @@ EOF</userinput></screen> <para>Logging on a system booted with systemd is handled with systemd-journald (by default), rather than a typical unix syslog daemon. - You can also add a normal syslog daemon and have both work side by + You can also add a normal syslog daemon and have both operate side by side if desired. The systemd-journald program stores journal entries in a binary format rather than a plain text log file. To assist with parsing the file, the command <command>journalctl</command> is provided. @@ -202,7 +203,7 @@ EOF</userinput></screen> chronological order.</para> </listitem> <listitem> - <para><command>journalctl -f</command>: povides functionality similar + <para><command>journalctl -f</command>: provides functionality similar to tail -f (follow).</para> </listitem> </itemizedlist> @@ -215,23 +216,23 @@ EOF</userinput></screen> <para>Core dumps are useful to debug crashed programs, especially when a daemon process crashes. On systemd booted systems the core dumping is handled by <command>systemd-coredump</command>. It will - log the core dump into the journal and store the core dump itself in + log the core dump in the journal and store the core dump itself in <filename class="directory">/var/lib/systemd/coredump</filename>. - To retrieve and process core dumps, <command>coredumpctl</command> + To retrieve and process core dumps, the <command>coredumpctl</command> tool is provided. Here are some examples of frequently used commands: </para> <itemizedlist> <listitem> <para><command>coredumpctl -r</command>: lists all core dumps in - reversed chronological order.</para> + reverse chronological order.</para> </listitem> <listitem> - <para><command>coredumpctl -1 info</command>: show the information - of the last core dump.</para> + <para><command>coredumpctl -1 info</command>: shows the information + from the last core dump.</para> </listitem> <listitem> - <para><command>coredumpctl -1 debug</command>: load the last core + <para><command>coredumpctl -1 debug</command>: loads the last core dump into <ulink url="&blfs-book;general/gdb.html">GDB</ulink>. </para> </listitem> @@ -249,7 +250,7 @@ cat > /etc/systemd/coredump.conf.d/maxuse.conf << EOF MaxUse=5G</literal> EOF</userinput></screen> - <para>See <filename>systemd-coredump(8)</filename>, + <para>See the <filename>systemd-coredump(8)</filename>, <filename>coredumpctl(1)</filename>, and <filename>coredump.conf.d(5)</filename> manual pages for more information.</para> @@ -284,7 +285,7 @@ EOF</userinput></screen> advantage of explicitly allowing and disallowing processes to run after the user session has ended, but breaks backwards compatibility with tools like <command>nohup</command> and utilities that use - <function>deamon()</function>. + <function>daemon()</function>. </para> </listitem> <listitem> @@ -298,7 +299,7 @@ EOF</userinput></screen> </listitem> <listitem> <para> - <emphasis>Disable at build-time</emphasis>: You can enable + <emphasis>Disable at build-time</emphasis>: You can disable lingering by default while building systemd by adding the switch <parameter>-Ddefault-kill-user-processes=false</parameter> to the <command>meson</command> command for systemd. This completely |