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

[Andrew Bower]

On Sun, Feb 02, 2025 at 08:45:25PM +0100, Lorenzo wrote:
> On Sun, 2 Feb 2025 19:24:45 +0000
> Andrew Bower <andrew at bower.uk> wrote:
> > diff --git a/debian/wtmpdb.wtmpdb-update-boot.init
> > b/debian/wtmpdb.wtmpdb-update-boot.init index d9213fc..4022d0f 100644
> > --- a/debian/wtmpdb.wtmpdb-update-boot.init
> > +++ b/debian/wtmpdb.wtmpdb-update-boot.init
> > @@ -15,10 +15,10 @@ fi
> >  # Provides:          wtmpdb-update-boot
> >  # Required-Start:    $remote_fs
> >  # Required-Stop:     $remote_fs
> > -# Should-Start:      dbus systemd-remount-fs systemd-tmpfiles-setup
> > -# Should-Stop:       dbus systemd-remount-fs systemd-tmpfiles-setup
> > -# Default-Start:     2 3 4 5
> > -# Default-Stop:      0 1 6
> > +# Should-Start:
> > +# Should-Stop:
> > +# Default-Start:     1 2 3 4 5
> 
> if $remote_fs insserv facility is mountnfs initscript, then
> Default-start can be runlevel S (it make sense to write the boot
> wtmp entry during boot runlevel, right?)

Thanks Lorenzo!

This is what I thought but it still doesn't get done in single user mode
until continuing boot. But I get a backtrace from plymouth in that case
anyway so that could be confounding the test. I'm planning to raise a
bug on plymouth and then de-install it then I can try again.

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

Cheers,

Andrew