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

[Lorenzo]

Hi all,

On Sun, 2 Feb 2025 19:24:45 +0000
Andrew Bower <andrew at bower.uk> wrote:

> 
> Actually, I see no reason to rely on most of these dependencies or
> wait until runlevel 2.
> 
> The dbus dependency is only for systemd to tell us about a "soft
> reboot", which is obviously not a thing in this case.

+ 1

> 
> How about this change? Seems to work ok.
> 
> 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?)

Cheers,
Lorenzo

> +# Default-Stop:      0 6
>  # Short-Description: Write boot and shutdown times into wtmpdb
>  # Description:       Invokes wtmpdb to write boot and shutdown times
>  #                    into the wtmpdb login database.
>