On 8/6/20 9:15 AM, David C. Rankin wrote:
On 8/5/20 2:28 PM, David C. Rankin wrote:
On 8/5/20 6:07 AM, Patrick Shanahan wrote:
please provide an example of an instance where "reboot needed" was provided and the reboot was not needed.
I'll get the zypper log or list of packages updated last night on 15.2 and post those later today. That will give us a baseline.
Here are the packages that were updated on 8/4 and none that I can tell would require a reboot, but nonetheless zypper stated Reboot Required:
# sed -n 's#^2020-08-04.*/\(\w\w*.*[.]rpm\)$#\1#p' < /var/log/zypper.log | sort -u diffutils-3.6-lp152.5.3.1.x86_64.rpm diffutils-lang-3.6-lp152.5.3.1.noarch.rpm ghostscript-9.52-lp152.2.4.1.x86_64.rpm ghostscript-x11-9.52-lp152.2.4.1.x86_64.rpm htop-2.2.0-lp152.3.6.x86_64.rpm libraw16-0.18.9-lp152.5.3.1.x86_64.rpm libsystemd0-234-lp152.31.4.1.x86_64.rpm libsystemd0-32bit-234-lp152.31.4.1.x86_64.rpm libudev1-234-lp152.31.4.1.x86_64.rpm systemd-234-lp152.31.4.1.x86_64.rpm systemd-bash-completion-234-lp152.31.4.1.noarch.rpm systemd-network-234-lp152.31.4.1.x86_64.rpm systemd-sysvinit-234-lp152.31.4.1.x86_64.rpm udev-234-lp152.31.4.1.x86_64.rpm
All can be updated without a reboot, the only two of consequence, systemd and udev can be handled with:
systemctl --system daemon-reexec udevadm control --reload-rules && udevadm trigger
So can we do something like this to minimize the number of reboots zypper calls for? Except for kernel updates, everything else should be able to be done without a reboot (there may be some others I'm not aware of), but systemd and udev shouldn't be two.
dbus is certainly one the current implementation has no way to track connections across restarts. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B