aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorXi Ruoyao <xry111@mengyan1223.wang>2022-03-16 15:49:35 +0800
committerXi Ruoyao <xry111@mengyan1223.wang>2022-03-16 15:49:35 +0800
commitccb08fafc839261488352388b5e708e6a845f0c5 (patch)
tree8e307603b537fd242403fe89460fb05c0797bcaf
parent16a517ac7ea84b93d1973f28f013a17219c2df94 (diff)
pkgmgmt: for systemd revision, add how to restart systemd without reboot
-rw-r--r--chapter08/pkgmgt.xml9
1 files changed, 8 insertions, 1 deletions
diff --git a/chapter08/pkgmgt.xml b/chapter08/pkgmgt.xml
index 3814b02b0..27e9c9cda 100644
--- a/chapter08/pkgmgt.xml
+++ b/chapter08/pkgmgt.xml
@@ -102,7 +102,7 @@
you have to downgrade a package, or the package changes the versioning
scheme of library files suddenly.</para> </listitem>
- <listitem> <para>If a package containing a shared library is updated,
+ <listitem><para>If a package containing a shared library is updated,
and the name of library doesn't change, but a severe issue
(especially, a security vulnerability) is fixed, all running programs
linked to the shared library should be restarted. The following
@@ -120,6 +120,13 @@
restart <command>sshd</command> service, then logout, login again,
and rerun that command to confirm nothing is still using the
deleted libraries.
+ </para>
+
+ <para revision='systemd'>
+ If the <command>systemd</command> daemon (running as PID 1) is
+ linked to the updated library, you can restart it without reboot
+ by running <command>systemctl daemon-reexec</command> as the
+ <systemitem class='username'>root</systemitem> user.
</para></listitem>
<listitem>