bug#64937: "who" reports funny dates

Hi, On Sun, Jul 30, Paul Eggert wrote: > Thorsten's draft coreutils patches > are a bit > long, and I'm hoping we can simplify this by packaging the fix inside > Gnulib (much as we already packaged the fix for not working on >

bug#64937: "who" reports funny dates

Hi, On Tue, Aug 01, Bruno Haible wrote: > Thorsten Kukuk wrote: > > If you haven't seen yet, I made some time ago a mapping > > between utmp struct entries and libsystemd functions: > > https://github.com/thkukuk/utmpx/blob/main/utmp-to-logind.md > > Thanks. This is helpful. > > The only pro

bug#64937: ssh sessions in systemd

On Wed, Aug 02, Bruno Haible wrote: > Thorsten Kukuk wrote: > > openssh is really special: it does not need a TTY for all kind of ssh > > sessions, and thus only opens a TTY if needed after creating the > > logind session. Thus the logind session does not contain the TTY > > informations. > > sy

bug#64937: "who" reports funny dates

Hi, On Fri, Aug 04, Paul Eggert wrote: > Thanks for doing all that work. I looked into it, and found a problem: a > command like "who /var/log/wtmp" stops working because the systemd > emulation of read_utmp only supports plain "who" (rougnly equivalent to > "who /var/run/utmp" on Fedora). S

bug#64937: "who" reports funny dates

On Sun, Aug 06, Paul Eggert wrote: > On 2023-08-03 23:53, Thorsten Kukuk wrote: > > And yes, "who /var/log/wtmp" will not work with this, too. But is this > > really a required or usefull use case? > > /usr/bin/last can give you the same output. > > Sure, but some people use "who" for that.[1][2]

bug#64937: "who" reports funny dates

On Sun, Aug 06, Paul Eggert wrote: > On 2023-08-06 13:00, Paul Eggert wrote: > > > How does "last" emulate /var/log/wtmp using systemd? > > Oh, I see from that wtmpdb comes > with its own "last". Is the plan to migrate this code into util-linux > "last", or

bug#64937: "who" reports funny dates

On Mon, Aug 07, Paul Eggert wrote: > On 2023-08-07 04:22, Bruno Haible wrote: > > > sooner than later. My guess is that Fedora and Ubuntu/Debian are only > > waiting for 'who' (coreutils) and 'last' (util-linux / wtmpdb) to > > stop accessing these two files. > > It's not just those two programs

bug#64937: "who" reports funny dates

On Tue, Aug 08, Bruno Haible wrote: > Thorsten Kukuk wrote: > > On musl libc systems like Alpine, > > you don't have utmp nor wtmp. > > But on Alpine Linux, I don't see a systemd nor a logind daemon. > How are logins meant to be recorded on this system? They don't record at all. Which means tool

bug#64937: "who" reports funny dates

On Tue, Aug 08, Robert Pluim wrote: > > On Tue, 8 Aug 2023 14:29:27 +, Thorsten Kukuk said: > Thorsten> Which means tools like who just don't show anything. And emacs > will > Thorsten> never find out the boot time with the current code. > > What API do you suggest we use instea

bug#64937: "who" reports funny dates

Hi, currently testing current coreutils git checkout on a utmp/wtmp free machine, looks good so far. Except there is a compile problem with this patch: On Tue, Aug 08, Bruno Haible wrote: > 2023-08-08 Bruno Haible > > readutmp: Get the boot time with higher precision. > Suggest

bug#64937: "who" reports funny dates

On Thu, Aug 10, Bruno Haible wrote: > This is merely a warning, and it's already gone after today's refactorings > in Gnulib. To get past it, either remove '-Werror' from the Makefile, or > bootstrap against the current Gnulib: Thanks, I know how to get past it, else I couldn't have tested the re

bug#65617: coreutils 9.4: seg.fault in readutmp with systemd

coreutils 9.4 with the --enable-systemd option seg.faults in lib/readutmp.c, line 801: for (session_ptr = sessions; *session_ptr != NULL; session_ptr++) If there is no session, "sessions" is NULL and "*session_ptr" will dereference a NULL pointer. Affected are who, pinky and uptime. A simple f

bug#65992: readutmp should check for sd_booted() and not if /run/utmp exists

Hi, if there is no /run/utmp file, /usr/bin/who falls back correctly to the systemd-logind interface and shows correct data. But there are applications, which don't use the libc interface for reading/writing utmp entries, they have their own implementation. And this implementations create the f

bug#65992: readutmp should check for sd_booted() and not if /run/utmp exists

Sorry, looks like strace confused me (since this checks the existence of /run/utmp) and the problem is a different one. kukuk@rubicon:~> ls /run/utmp ls: cannot access '/run/utmp': No such file or directory kukuk@rubicon:~> w 14:54:41 up 4 days, 4:51, 2 users, load average: 0,11, 0,13, 0,46

bug#73928: Bug#1080330: coreutils: who no longer works

On Mon, Feb 17, 2025 at 10:08 AM Paul Eggert wrote: > Even if it's that simple, something is updating the traditional > /var/run/utmp and /var/log/wtmp files on Fedora and Ubuntu and at least > in some cases they work better than systemd does and this should be > fixed somehow. Applications are

bug#73928: Bug#1080330: coreutils: who no longer works

Hi, Let me clarify some things. On Sun, Feb 16, 2025 at 11:52 PM Paul Eggert wrote: > > At this point I confess I don't know what changes would be needed for > GNU 'who'. I see a difference of opinion as to whether 'w' works. There > seem to be multiple mechanisms in play (utmp, wtmp, wtmpdb, la

bug#73928: Bug#1080330: coreutils: who no longer works

On Mon, Feb 17, 2025 at 8:40 AM Paul Eggert 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 di

bug#73928: Bug#1080330: coreutils: who no longer works

On Mon, Feb 17, 2025 at 10:25 AM Vincent Lefevre wrote: > > On 2025-02-17 08:03:23 +0100, Thorsten Kukuk wrote: > > Some terminal applications (e.g. xterm, konsole, ...) create fake utmp > > entries for historic reasons: so that broadcast messages are shown in > > every single terminal. Which for