bug#64954: GNU 'uptime' on OpenBSD always prints "0 users"

2023-07-30 Thread Paul Eggert
On 2023-07-30 11:41, Pádraig Brady wrote: I'm fine with the change, but we'll also need to adjust the sc_prohibit_always_true_header_tests syntax check in gnulib I looked into that but it's such a hassle that I came up with the attached simpler patch to Coreutils. How about installing it

bug#64954: GNU 'uptime' on OpenBSD always prints "0 users"

2023-07-30 Thread Pádraig Brady
On 30/07/2023 15:44, Bruno Haible wrote: Hi, GNU coreutils-9.3 'uptime', on OpenBSD 7.2, prints 16:24:53 up 14 days 13:33, 0 users, load average: 0.04, 0.44, 0.59 whereas the OpenBSD /usr/bin/uptime prints 4:24PM up 14 days, 13:33, 1 user, load averages: 0.04, 0.44, 0.59 The utmp

bug#64937: "who" reports funny dates

2023-07-30 Thread Bruno Haible
Paul Eggert wrote: > If I understand that discussion correctly, the idea is to switch from > utmp/utmpx to the systemd interface once systemd 254 comes out. > > As it happens, systemd 254 was published Friday. It's already contained in Fedora Rawhide. > It'd be good to get it working with

bug#64937: "who" reports funny dates

2023-07-30 Thread Paul Eggert
On 2023-07-30 04:02, Pádraig Brady wrote: Yes I think the consensus is to switch away from the utmp API, which was recently discussed at: https://lists.gnu.org/archive/html/coreutils/2023-06/msg00024.html If I understand that discussion correctly, the idea is to switch from utmp/utmpx to the

bug#64937: "who" reports funny dates

2023-07-30 Thread Sven Joachim
On 2023-07-29 17:30 -0700, Paul Eggert wrote: > On 2023-07-29 12:44, Pádraig Brady wrote: >> I tried a quick build with -D__WORDSIZE_TIME64_COMPAT32=1 >> which is what glibc uses to force the smaller time types. >> However that didn't fix the issue, so I'll need to look a bit more, >> and how to

bug#64937: "who" reports funny dates

2023-07-30 Thread Pádraig Brady
On 30/07/2023 01:30, Paul Eggert wrote: On 2023-07-29 12:44, Pádraig Brady wrote: I tried a quick build with -D__WORDSIZE_TIME64_COMPAT32=1 which is what glibc uses to force the smaller time types. However that didn't fix the issue, so I'll need to look a bit more, and how to get only utmp