Antw: Re: suggestion: auto reload as the default to help packagers?

["Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>]

>>> Michael Chapman <mike@xxxxxxxxxxxxxxxxx> schrieb am 31.05.2019 um 13:28 in
Nachricht <alpine.LFD.2.21.1905312123080.3180@xxxxxxxxxx>:
> On Fri, 31 May 2019, Reindl Harald wrote:
>> 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
> 
> I actually got it slightly wrong: %transfiletriggerin and 
> %transfiletriggerun occur in the _middle_ of the transaction, in between 
> installation of new packages (or new versions of packages) and removal of 
> old packages (or old versions of packages). While %transfiletriggerin 
> does perform a daemon-reload, %transfiletriggerun simply stores a 
> flag that's picked up by a separate %filetriggerpostun scriptlet. That 
> reloads systemd.

Where is the definitive documentation for these (rather new) RPM features?
And do all the major RPM-based dirstributions support these?

Regards,
Ulrich
[...]


_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel