On 4/3/25 2:58 PM, Antonio Terceiro wrote:
On Tue, Apr 01, 2025 at 03:27:05PM -0400, Michael Stone wrote:/run/utmp is no longer provided in trixie, which means that the mechanisms used to show active sessions in unix for several decades no longer work. There's a replacement mechanism provided by systemd, but it's not 1:1. I propose that for trixie *both* mechanisms are active, so a person can choose between them (and compare the output, to better identify gaps between the historic utmp mechanism and the new and improved systemd facility). I've been told that the reason this can't be done is that utmp isn't y2038 compliant, but it seems to me that we won't be supporting trixie in y2038, so who cares? Are there any factors to consider that I've missed?I never cared about /run/utmp in itself, but I got used to last(1). FWIW, a new implementation of last is now provided by wtmpdb.
+1 great, it looks like that * wtmpdb(8) could be a well alternative to who(1), as the discussed alternatives w(1) and loginctl(1) are not listing su(1) sessions. The program arguments are not fully compatible with Unix equivalent last(1). I.e. it seems not to be possible to just filter out all current still active sessions, which should be provided by `last -p` in the Unix world. Here an example output ``` $> last -S | grep -- '- still'root pts/0 su Fri Apr 4 21:06 - still logged in dirk pts/2 su Fri Apr 4 21:05 - still logged in dirk tty1 login Fri Apr 4 21:04 - still logged in dirk tty7 :0 lightdm Fri Apr 4 20:26 - still logged in reboot system boot 6.12.20-amd64 Fri Apr 4 20:25 - still running
``` Additionally, I fount a Debian-Wiki entry for that topic * https://wiki.debian.org/pam_lastlog2%20and%20wtmpdb Greets, Dirk =)
OpenPGP_signature.asc
Description: OpenPGP digital signature
