Luca Boccassi: > Source: debhelper > Priority: wishlist > Tags: bookworm > X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org > > Dear Maintainer(s), > > systemd v248 will ship with a new dbus/systemctl interface to mark a > unit as needing reload/restart, and a new dbus/systemctl to queue all > reload/restart jobs in a single command. > The RPM packaging/scripts are changing to use this instead of custom > batching. > > I'm opening this ticket to explore whether it would be > possible/good/desirable to switch the debhelper tools to use this as > well in the future. > > It looks like this: > > systemctl set-property foo.service Markers=needs-restart > systemctl set-property bar.service Markers=needs-reload > ... > systemctl reload-or-restart --marked > > (or equivalent DBUS calls) > > References: > > https://github.com/systemd/systemd/commit/ff68472a20c208121b69ea13586f3105a219bc14 > https://github.com/systemd/systemd/commit/c9615f73521986b3607b852c139036d58973043c > https://github.com/systemd/systemd/pull/18481/commits > > The advantage being, you can mark a unit inline, but then batch the > actual jobs later/asynchronously. > > Note that, given the interface has just been merged and is not yet > released, there is scope for improvements if there are debhelper- > specific concerns to address, given the feature first use is the RPM's > side of things. > > Thoughts? >
By the sound of it, this is something that might need to go into the init system helpers that debhelper invokes in the maintscripts (possibly with a trigger in the systemd side to do the batch reload/restart). @Michael: What is your view? ~Niels
