Hi,
On Fri, 7 Feb 2025 23:34:28 +
Andrew Bower wrote:
> > > What about /etc/runit/override-sysv.d?
> >
> > yes, that would work too, I can ship the file with runit-init
> > package.
>
> Like this? Trivial patch here works for me, although I put it in the
> wrong package!
>
> I thought a .
Hi Lorenzo,
On Sun, Feb 02, 2025 at 11:52:25PM +0100, Lorenzo wrote:
> On Sun, 2 Feb 2025 22:25:43 +
> Andrew Bower wrote:
>
> > On Sun, Feb 02, 2025 at 11:00:46PM +0100, Lorenzo wrote:
> > > On Sun, 2 Feb 2025 21:00:41 +
> > > Andrew Bower wrote:
> > >
> > > For the boot entry I can j
Control: tags -1 + patch
On Mon, Feb 03, 2025 at 09:05:59AM +, Mark Hindley wrote:
> control: reassign -1 wtmpdb
>
> Andrew,
>
> This seems to be resolvable in wtmpdb, so I am reassigning.
https://salsa.debian.org/abower/wtmpdb/-/commit/bfcc651ba54f2edec3cb502968db21556d0cb47e
https://salsa
control: reassign -1 wtmpdb
Andrew,
This seems to be resolvable in wtmpdb, so I am reassigning.
Best wishes
Mark
On Sun, Feb 02, 2025 at 02:26:20AM +0100, Chris Hofstaedtler wrote:
> Providing initscripts would IMO be sensible; for systemd wmptdb
> provides two .service files as integration.
Yes, unit-translator converts wtmpdb-rotate to:
# Generated by /home/mark/src/debian/unit-translator/utrans from:
#
On Sun, Feb 02, 2025 at 11:00:46PM +0100, Lorenzo wrote:
> On Sun, 2 Feb 2025 21:00:41 +
> Andrew Bower wrote:
>
> 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
On Sun, Feb 02, 2025 at 08:45:25PM +0100, Lorenzo wrote:
> On Sun, 2 Feb 2025 19:24:45 +
> Andrew Bower 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
> > ++
Mark,
On Sun, Feb 02, 2025 at 04:16:29PM +, Andrew Bower wrote:
> On Sat, Feb 01, 2025 at 08:32:28PM +, Mark Hindley wrote:
> > On Sat, Feb 01, 2025 at 08:23:51PM +, Mark Hindley wrote:
> > > Andrew,
> > >
> > > I suppose adding something in initscripts might be possible.
> >
> > Act
Mark,
On Sat, Feb 01, 2025 at 08:32:28PM +, Mark Hindley wrote:
> On Sat, Feb 01, 2025 at 08:23:51PM +, Mark Hindley wrote:
> > Andrew,
> >
> > I suppose adding something in initscripts might be possible.
>
> Actually, is there a reason why this or something similar should be included
>
On Sat, Feb 01, 2025 at 08:23:51PM +, Mark Hindley wrote:
> Chris,
>
> Thanks for your input as well.
>
> I notice that wtmpdb is orphaned[1] and you have preemptively declined to
> comment
> on the reason, which I respect. Is it reasonable to infer the wtmpdb is not
> going to have longevit
On Sat, Feb 01, 2025 at 08:23:51PM +, Mark Hindley wrote:
[to Chris]
> Is it reasonable to infer the wtmpdb is not
> going to have longevity as a solution here?
With the upstream effort focussed on a long-running daemon to solve a
file-locking problem, I suspect we need to look after v0.13 for
Hi Mark,
On Sat, Feb 01, 2025 at 08:32:28PM +, Mark Hindley wrote:
> On Sat, Feb 01, 2025 at 08:23:51PM +, Mark Hindley wrote:
> > Andrew,
> >
> > I suppose adding something in initscripts might be possible.
>
> Actually, is there a reason why this or something similar should be included
On Sat, Feb 01, 2025 at 08:23:51PM +, Mark Hindley wrote:
> Andrew,
>
> I suppose adding something in initscripts might be possible.
Actually, is there a reason why this or something similar should be included in
wtmpdb itself?
Mark
#! /bin/sh
# Generated by /home/mark/src/debian/unit-trans
Andrew,
I suppose adding something in initscripts might be possible.
Chris,
Thanks for your input as well.
I notice that wtmpdb is orphaned[1] and you have preemptively declined to
comment
on the reason, which I respect. Is it reasonable to infer the wtmpdb is not
going to have longevity as a
On Sat, Feb 01, 2025 at 01:27:15PM +, Andrew Bower wrote:
> Any thoughts on:
>
> - install an initscript with wtmpdb that imports the missing real wtmp
>entries into wtmpdb at boot.
> - install an initscript with wtmpdb independently to record startup and
>shutdown, but less reliably
Package: sysvinit-core
Version: 3.13-1
Severity: normal
sysvinit-core does not write entries to the new wtmpdb.
I fully understand how deeply unattractive the idea would be of any of
the following approaches to doing this:
- linking with libwtmpdb
- spawning wtmpdb
- doing anything more direc
16 matches
Mail list logo
