Changeset ab9b18b

08/09/2016 05:53:37 AM (7 years ago)
DJ Lucas <dj@…>
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, 8.0, 8.1, 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/parallelism, xry111/pip3, xry111/rust-wip-20221008

Added explanatory text for systemd-230+ process lingering changes.

git-svn-id: 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

4 edited


  • chapter01/changelog.xml

    rc8389f0 rab9b18b  
    4343    appropriate for the entry or if needed the entire day's listitem.
     45   <listitem revision="systemd">
     46      <para>2016-08-09</para>
     47      <itemizedlist>
     48        <listitem>
     49          <para>[dj] - Added explanatory text for systemd-230+ process
     50          lingering changes.</para>
     51        </listitem>
     52      </itemizedlist>
     53   </listitem>
    4555   <listitem>
    4656      <para>2016-08-06</para>
  • chapter07/systemd-custom.xml

    rc8389f0 rab9b18b  
    175175  </sect2>
     177  <sect2>
     178    <title>Long Running Processes</title>
     180    <para>Beginning with systemd-230, all user processes are killed when a
     181    user session is ended, even if nohup is used, or the process uses
     182    <function>daemon()</function> or <function>setsid()</function>. This is a
     183    deliberate change from a historically permissive environment to a more
     184    restrictive one. The new behavior may cause issues if you depend on long
     185    running programs (e.g., <command>screen</command> or
     186    <command>tmux</command>) to remain active after ending your user
     187    session. There are three ways to enable lingering processes to remain after
     188    a user session is ended.</para>
     190    <itemizedlist>
     191      <listitem>
     192        <para>
     193          <emphasis>Enable process lingering for only needed users</emphasis>:
     194          normal users have permission to enabling process lingering
     195          with the command <command>loginctl enable-linger</command> for their
     196          own user. System administrators can use the same command with a
     197          <parameter>user</parameter> argument to enable for a user. That user
     198          can then use the <command>systemd-run</command> command to start
     199          long running processes. For example: <command>systemd-run --scope
     200          --user /usr/bin/screen</command>. If you enable lingering for your
     201          user, the user@.service will remain even after all login sessions are
     202          closed, and will automatically start at system boot. This has the
     203          advantage of explicitly allowing and disallowing processes to run
     204          after the user session has ended, but breaks backwards compatibility
     205          with tools like <command>nohup</command> and utilities that use
     206          <function>deamon()</function>.
     207        </para>
     208      </listitem>
     209      <listitem>
     210        <para>
     211          <emphasis>Enable system-wide process lingering</emphasis>:
     212          you can set <parameter>KillUserProcesses=no</parameter> in
     213          <filename>/etc/logind.conf</filename> to enable process lingering
     214          globally for all users. This has the benefit of leaving the old
     215          method available to all users at the expense of explicit control.
     216        </para>
     217      </listitem>
     218      <listitem>
     219        <para>
     220          <emphasis>Disable at build-time</emphasis>: You can enable
     221          lingering by default while building systemd by adding the switch
     222          <parameter>--without-kill-user-processes</parameter> to the
     223          <command>configure</command> command for systemd. This completely
     224          disables the ability of systemd to kill user processes at session
     225          end.
     226        </para>
     227      </listitem>
     228    </itemizedlist>
     230  </sect2>
  • general.ent

    rc8389f0 rab9b18b  
    1 <!ENTITY version         "SVN-20160805">
     1<!ENTITY version         "SVN-20160809">
    22<!ENTITY short-version   "svn">  <!-- Used below in &blfs-book;
    33                                      Change to x.y for release but not -rc releases -->
    44<!ENTITY generic-version "development"> <!-- Use "development"  or "x.y[-pre{x}]" -->
    6 <!ENTITY versiond        "20160806-systemd">
     6<!ENTITY versiond        "20160809-systemd">
    77<!ENTITY short-versiond  "systemd">
    88<!ENTITY generic-versiond "systemd">
    10 <!ENTITY releasedate     "August 6, 2016">
     10<!ENTITY releasedate     "August 9, 2016">
    1111<!ENTITY copyrightdate   "1999-2016"><!-- jhalfs needs a literal dash, not &ndash; -->
    1212<!ENTITY milestone       "7.10">
  • packages.ent

    rc8389f0 rab9b18b  
    190190<!ENTITY flex-version "2.6.1">
    191 <!ENTITY flex-size "916 KB">
     191<!ENTITY flex-size "816 KB">
    192192<!ENTITY flex-url ";/flex-&flex-version;.tar.xz">
    193193<!ENTITY flex-md5 "cd3c86290fc2676a641aefafeb10848a">
Note: See TracChangeset for help on using the changeset viewer.