On Sun, Jun 18, Jan Engelhardt wrote:
On Friday 2023-06-16 14:04, Thorsten Kukuk wrote:
I have a repository with, where I modified the applications to query logind instead reading /run/utmp: - systemd (utmp disabled, backports from git added) - coreutils - util-linux - procps - pam - openssh - monitoring-plugins - net-snmp
Afterwards, there should be no /run/utmp anymore. If an application still creates this file and writes into it, it does not use the glibc API and we have to fix that.
What do you think about making a FUSE-based "utmpfs" that provides just one file (a utmp representation of logind state), bind-mounted to /run/utmp.
??? The utmp format and the API is not Y2038 safe and has many design and security issues. I don't see how your solution solves a single problem of the many problems.
I'm especially interested in your experience with who, w, uptime and from people, who use check_users from monitoring-plugins or read the number of users with net-snmp.
screen/xterm/tmux
??? screen and xterm write useless utmp entries as this are no login sessions, our tmux does not write utmp entires (or did not when I analysed this), gnome-terminal does not write, ksonsole does write, ... So a big chaos, which makes /run/utmp unreliable for everything. Another problem we want to solve with this. And why several upstream projects like the idea. 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 Myers, Andrew McDonald, Martje Boudien Moerman (HRB 36809, AG Nürnberg)