[systemd-devel] suggestion: auto reload as the default to help packagers?

Reindl Harald h.reindl at thelounge.net
Fri May 31 11:09:28 UTC 2019

Am 31.05.19 um 12:31 schrieb Michael Chapman:
> For RPM on Fedora, the systemd package has %transfiletriggerin and 
> %transfiletriggerun scriptlets that run automatically at the end of the 
> RPM transaction if units were installed or removed. This is the cleanest 
> approach since it means all changes from all updated packages are applied 
> at once.

sadly that's all theory given that all services in Fedora are
automatically hard restartet when packages are updated and "at the end"
is too late when the service got restarted with the old unit but new binary

you notice that when you upgrade your system with "dnf --releasever=29
distro-sync" where you get warnings about changed unit files and in case
of F29 for example samba which would happily run until you reboot the
machine crashs often enough because of old and new libs to finally fail it

no, go away with "offline updates", not after 20 dist-upgrades on 30
machines over more than a decade :-)

every automatic service restart is a pain in the ass in context of
"sysadmin can't prepare a set of interconnected changes" to satisfy
noobs which won't restart by hand and it's the main reason that i build
every business critical server package at my own all the years besides

this stuff should be either completly ripped off and replaced by some
GUI notify or at least with a global switch to disable that behavior

on servers amdins are expected to know what they are doing and with a
incompatible config change that#s all doomed to fail because you either
have a invalid config for the version before the update or it crashs
because of the restart due upgrade

More information about the systemd-devel mailing list