Hi Mark, On 2024-06-13 10:26, Mark Hindley wrote: > Aurelien, > > On Sun, Jun 09, 2024 at 08:51:34PM +0100, Mark Hindley wrote: > > Until that happens, does that mean that sysvinit will be restarted twice, > > once by > > libc6 postinst and once by the libc-upgrade trigger? > > For the record, this appears to be the case: > > $ dpkg-reconfigure libc6 > > logs in /var/log/syslog: > > Jun 13 10:11:21 DebianUnstable init: Trying to re-exec init > Jun 13 10:11:23 DebianUnstable init: Trying to re-exec init > > I suppose it isn't a show-stopper, but it is ugly. Do you see a way to avoid > it?
Yes, this is indeed a side effect, that we will have to leave with for some time. The goal is to reduce it as much as possible, and in anycase to get that done before the trixie release. My idea is to remove the old restart mechanism once all init systems have added the trigger support. For that we probably wants to add a Breaks against the init system version older than the one implementing the change. So far this has been implemented in systemd, and sysvinit (but not yet uploaded). TTBOMK, the only other one that need to get support is finit. I will see if I can come with a patch to move things forward. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
