Bug#1094921: sysvinit-core: does not write entries to wtmpdb

Lorenzo plorenzo at disroot.org
Sun Feb 2 22:00:46 GMT 2025


On Sun, 2 Feb 2025 21:00:41 +0000
Andrew Bower <andrew at bower.uk> wrote:

> 
> When this is done do you have an obvious method to mask out the
> initscript for runit users?

not really, there is no runit service for this, and since it's a
oneshot there's not going to be one to mask the sysv script.
For the boot entry I can just remove the wtmpdb call in stage 1; for the
shutdown entry in runit, is implemented as "halt -w[1]" in shutdown.c
that is called by umountnfs.sh in runlevel 0 or 6, and it's not obvious
to me how to prevent a double shutdown entry here.
maybe the sysv script can be a no-op when runit is init?

[ -f  /run/runit.stopit ] && exit 0

better ideas are welcome; when I added the code to runit I didn't think
a sysv script was going to be accepted in the wtmpdb package.

[1] by the way, what's the plan for 'halt -w' in SysV 's shutdown
implementation?

Lorenzo

> 
> Cheers,
> 
> Andrew



More information about the Debian-init-diversity mailing list