Changeset 0d84af1 for chapter07/systemd-custom.xml

Timestamp:

12/28/2017 03:52:38 AM (6 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

25332b5

Parents:

9fde3e9

Message:

Typos and wording changes

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11343 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter07/systemd-custom.xml (modified) (3 diffs)

chapter07/systemd-custom.xml

@@ -22 +22 @@
     entries commented out with the default settings indicated. This file is
     where the log level may be changed as well as some basic logging settings.
-    See <filename>systemd-system.conf(5)</filename> manual page for details on
-    each configuration option.</para>
+    See the <filename>systemd-system.conf(5)</filename> manual page for details
+    on each configuration option.</para>
 
   </sect2>
@@ -213 +213 @@
     <title>Long Running Processes</title>
 
-    <para>Beginning with systemd-230, all user processes are killed when a
-    user session is ended, even if nohup is used, or the process uses
-    <function>daemon()</function> or <function>setsid()</function>. This is a
-    deliberate change from a historically permissive environment to a more
-    restrictive one. The new behavior may cause issues if you depend on long
-    running programs (e.g., <command>screen</command> or
-    <command>tmux</command>) to remain active after ending your user
-    session. There are three ways to enable lingering processes to remain after
-    a user session is ended.</para>
+    <para>Beginning with systemd-230, all user processes are killed when a user
+    session is ended, even if nohup is used, or the process uses the
+    <function>daemon()</function> or <function>setsid()</function> functions.
+    This is a deliberate change from a historically permissive environment to a
+    more restrictive one. The new behavior may cause issues if you depend on
+    long running programs (e.g., <command>screen</command> or
+    <command>tmux</command>) to remain active after ending your user session.
+    There are three ways to enable lingering processes to remain after a user
+    session is ended.</para>
 
     <itemizedlist>
       <listitem>
         <para>
-          <emphasis>Enable process lingering for only needed users</emphasis>:
-          normal users have permission to enable process lingering
+          <emphasis>Enable process lingering for only selected users</emphasis>:
+          Normal users have permission to enable process lingering
           with the command <command>loginctl enable-linger</command> for their
           own user. System administrators can use the same command with a
@@ -245 +245 @@
         <para>
           <emphasis>Enable system-wide process lingering</emphasis>:
-          you can set <parameter>KillUserProcesses=no</parameter> in
+          You can set <parameter>KillUserProcesses=no</parameter> in
           <filename>/etc/logind.conf</filename> to enable process lingering
           globally for all users. This has the benefit of leaving the old