Am 18.07.19 um 15:54 schrieb Laurent Bigonville: > On 18/07/19 15:09, Michael Biebl wrote: >> Am 18.07.19 um 14:40 schrieb Laurent Bigonville:
>> What we might do is to run daemon-reload implicitly via a dpkg >> file-trigger. This would cover cases like yours. >> Not sure. Thoughts? > > Is it a good idea to have a different way of calling daemon-reload only > for this case? > > In the other cases you still need to do that synchronously My idea was, to avoid unnecessary daemon-reloads as much as possible. If your use case is, that at some point in the future, the user might (re)start the service, then it is sufficient if we do a single daemon-reload after the dpkg run. Let's say we have 10 packages using "--no-start --no-restart-after-upgrade", then a single daemon-reload at the end would be sufficient instead of having to directly call daemon-reload from postinst. On the other hand, having a dpkg file-trigger for /lib/system/system would mean we trigger daemon-reload at least twice for the common case (one via postinst and one via file trigger). -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
