From: Florian Weimer <fw@deneb.enyo.de>
To: Roman Bakshansky <bakshansky.lists@gmail.com>
Cc: linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
audit@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: [RFC] Modernizing Linux authentication logs (lastlog, btmp, utmp, wtmp) with SQLite
Date: Fri, 13 Mar 2026 19:51:31 +0100 [thread overview]
Message-ID: <87cy175zrg.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <660c10e6-f8b5-46e2-a424-e3e052992b3a@gmail.com> (Roman Bakshansky's message of "Fri, 13 Mar 2026 00:01:25 +0300")
* Roman Bakshansky:
> The full RFC, including preliminary database schemas and API drafts,
> is available in the discussion repository:
>
> https://github.com/bakshansky/linux-auth-logs
I don't understand how SQLite (without a daemon) addresses the locking
issue. WAL mode still uses fcntl locking.
prev parent reply other threads:[~2026-03-13 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 21:01 [RFC] Modernizing Linux authentication logs (lastlog, btmp, utmp, wtmp) with SQLite Roman Bakshansky
2026-03-13 13:59 ` Adhemerval Zanella Netto
2026-03-13 14:45 ` Vincent Lefevre
2026-03-13 17:49 ` Roman Bakshansky
2026-03-13 17:48 ` Roman Bakshansky
2026-03-13 18:03 ` Adhemerval Zanella Netto
2026-03-13 18:51 ` Florian Weimer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cy175zrg.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=audit@vger.kernel.org \
--cc=bakshansky.lists@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox