GNU bug report logs - #73928
"who" should support wtmpdb

Previous Next

Full log

Message #54 received at 73928 <at> debbugs.gnu.org (full text, mbox):

From: Thorsten Kukuk <kukuk <at> suse.com>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: Gnulib bugs <bug-gnulib <at> gnu.org>, 1080330 <at> bugs.debian.org,
 Chris Hofstaedtler <zeha <at> debian.org>, Vincent Lefevre <vincent <at> vinc17.net>,
 Michael Stone <mstone <at> debian.org>, 73928 <at> debbugs.gnu.org
Subject: Re: bug#73928: Bug#1080330: coreutils: who no longer works
Date: Mon, 17 Feb 2025 09:22:09 +0100

On Mon, Feb 17, 2025 at 8:40 AM Paul Eggert <eggert <at> cs.ucla.edu> wrote:
>
> On 2025-02-16 23:03, Thorsten Kukuk wrote:
> > The problems were already all solved with the first coreutils versions
> > having systemd-logind support.  Even with all the bug reports I don't
> > see a need for changes in Coreutils, only in distributions not
> > enabling systemd-logind support in all packages.
>
> Thanks for the summary. Unfortunately I'm not seeing all the problems
> solved, at least not on current Fedora (41) and Ubuntu (24.10).
>
> If I configure current (f2e323430193956709aacca33f6b4fcab4fb9d8b)
> Coreutils with --enable-systemd on my Ubuntu 24.10 desktop, the output
> gets worse:
>
>    $ ./who-no-systemd # Configured normally.
>    eggert   seat0        2025-02-15 10:11 (login screen)
>    eggert   tty2         2025-02-15 10:11 (tty2)
>    $ ./who-with-systemd # Configured with --enable-systemd.
>    eggert   seat0        2025-02-15 10:11
>    eggert   tty2         2025-02-15 10:11
>
> Apparently for coreutils, /var/run/utmp (the traditional interface) has
> more info than libsystemd's API. (For what it's worth, both versions of
> "who" consult /var/run/utmp on Ubuntu 24.10, but the systemd version
> also consults /run/systemd/sessions/*.)

systemd-logind provides the same info as utmp does, I made sure that
this is the case and available:
https://github.com/thkukuk/utmpx/blob/main/utmp-to-logind.md

And who (with --enable-systemd with no /run/utmp on openSUSE Tumbleweed):
On a server:
kukuk    pts/3        2025-02-12 11:20 (192.168.122.1)
kukuk    pts/0        2025-02-11 12:00 (192.168.122.1)
kukuk    pts/1        2025-02-11 14:26 (192.168.122.1)

On my local machine with KDE:
kukuk    seat0        2025-02-11 15:58 (:0)
kukuk    tty2         2025-02-11 15:58 (:0)
root     pts/2        2025-02-15 18:32

No idea why this is not working for you. On openSUSE we have no
additional patches which are not upstream.
Maybe that systemd version is too old on that systems?

> Similarly, on a Fedora 41 desktop where I'm not currently logged in, I
> get inferior results when Coreutils is configured with --enable-systemd:
>
>    $ ./who-no-systemd
>    eggert   pts/3        2025-02-16 22:56 (47.147.225.25)
>    $ ./who-with-systemd
>    gdm      seat0        2025-02-13 18:04
>    gdm      tty1         2025-02-13 18:04
>    eggert   sshd pts/3   2025-02-16 22:56 (47.147.225.25)
>
> Here, though I'm logged in only via ssh, the libsystemd-using 'who'
> incorrectly reports that a user named "gdm" is logged in in person.
>
> My guess is that, once systemd was changed to continue to output via the
> traditional /var/run/utmp and /var/log/wtmp files, people stopped
> configuring coreutils with --enable-systemd and stopped worrying about
> making sure that the more-modern systemd API works, which means that the
> traditional files are still essential.

systemd  only writes the boot time, nothing else.

Thorsten
-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies
SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461
Nuernberg, Germany
Managing Director: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB
36809, AG Nürnberg)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.