Re: who/uptime segfaults if DISPLAY=:0 is missing in logind session

On Fri, Sep 15, Thorsten Kukuk wrote: > On Fri, Sep 15, Bruno Haible wrote: > > > Thorsten Kukuk wrote: > > > With gdm there are reports that who/uptime seg.fault. > > > > Please make it easy to reproduce for me. I had tested 6 different init > &g

Re: who/uptime segfaults if DISPLAY=:0 is missing in logind session

On Fri, Sep 15, Bruno Haible wrote: > Thorsten Kukuk wrote: > > With gdm there are reports that who/uptime seg.fault. > > Please make it easy to reproduce for me. I had tested 6 different init > systems [1] and 10 different desktop environments. That's why I added the ses

who/uptime segfaults if DISPLAY=:0 is missing in logind session

5 226:1 13:67 13:66 -- 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)

Re: readutmp should check for sd_booted() and not if /run/utmp exists

n with sddm, login, sshd or so. Since I don't use GNOME, I cannot reproduce. The seg.faults are new reports. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany Managing

Re: readutmp backlog

On Mon, Sep 11, Paul Eggert wrote: > On 9/10/23 11:27, Thorsten Kukuk wrote: > > So from my view, I currently don't see something better than wtmpdb and > > I don't see anybody working on a different solution. > > Thanks for the heads-up. > > I now also

Re: readutmp backlog

ecause we glibc still implements the functions and we don't want to patch all applications writing wtmp entries. ALP, our next code base for our enterprise products, made the switch already, too. So from my view, I currently don't see something better than wtmpdb and I don't see anybod

Re: bug#64937: "who" reports funny dates

se I couldn't have tested the result ;) I only wanted to make aware of it, so that it does not go lost, since this warning doesn't happen in all configurations. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany G

Re: bug#64937: "who" reports funny dates

precision. > Suggested by Thorsten Kukuk in > > <https://github.com/thkukuk/utmpx/blob/main/utmp-to-logind.md#determine-boot-time>. > * lib/readutmp.c (get_boot_time_uncached): Try clock_gettime first. > > diff --git a/lib/readutmp.c b/lib/readutmp.c > index 7ef5b

Re: bug#64937: "who" reports funny dates

On Tue, Aug 08, Robert Pluim wrote: > >>>>> On Tue, 8 Aug 2023 14:29:27 +0000, 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 cod

Re: 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? The

Re: bug#64937: "who" reports funny dates

ot logged. I know that Fedora tries to maintain it via pam_lastlog.so, but do to all the problems with this interface that module is deprecated and will be removed in a future release. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software So

Re: bug#64937: "who" reports funny dates

tools like "last" did not yet exist. > Also, the question about /var/adm/btmp remains. Is there a use-case, for which it is __reliable__ useable? Until now, nobody could tell me one and nobody cared. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Te

Re: 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

Re: bug#64937: "who" reports funny dates

issue. For this reason we (openSUSE/SUSE) switched to wtmpdb: https://github.com/thkukuk/wtmpdb and don't support /var/log/wtmp anymore. 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.

Re: 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

Re: 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

Re: bug#64937: "who" reports funny dates

ames, user names and host names. 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)