Bug#1105954: openssh-server: OpenSSH produces error on logout because utmp is no longer used

["Trent W. Buck" <trentbuck@gmail.com>]

Hi, I am a nosy bystander.

I see this log event on my Debian 13 systems.
I think this is because my systems have neither utmp nor wtmpdb.
I think on such systems, this error message is SAFE TO IGNORE.
I would still like this log event to be generated in the first place
(maybe with something like DoWtmp=no in /etc/ssh/sshd_config.d/foo.conf).

Here are some cross-references that are relevant:

utmp/wtmp are gone, wtmpdb is opt-in and not recommended:
https://www.debian.org/releases/trixie/release-notes/issues.html#the-last-lastb-and-lastlog-commands-have-been-replaced

openssh/trixie has wtmpdb enabled:
https://www.openssh.com/txt/release-10.0#line=236
https://sources.debian.org/src/openssh/1%3A10.0p1-7/debian/rules#L90

the error message is where openssh calls logout(), which seems to be 
glibc updating utmp(5):
https://sources.debian.org/src/openssh/1%3A10.0p1-7/loginrec.c#L1480-L1500
https://manpages.debian.org/trixie/manpages-dev/logout.3.en.html
https://sourceware.org/glibc/manual/2.41/html_node/Logging-In-and-Out.html

I can't see anything in "man sshd_config" or in the code to let me 
disable this.
I suspect "apt install wtmdb" is sufficient to make the log event go 
away, but
at the cost of doing needless work (doing a sqlite3 UPSERT on logout).
I have not yet tested this suspicion.