After the recent change replacing last/wtmp with wtmpdb, all tty7 entries back to the first entry show “still logged in”. Is not showing logout times a bug or (not useful) feature?
Y2038 transitions need to be done better. There is no rush to replace things that won’t break for 15 years so why do a harsh transition where the old is completely eliminated? Why not run both for the transition period?
At least wtmp is still being generated even if all the tools to look at it were removed. I had to track down and compile the source for last to show this problem.
Output of old last:
mee pts/1 :0.0 Sun Jul 23 05:35 still logged in
mee pts/0 :0.0 Sun Jul 23 05:01 still logged in
mee console :0 Sun Jul 23 05:01 gone - no logout
reboot system boot 6.4.3-1-default Sun Jul 23 05:01 still running
mee pts/1 :0.0 Sat Jul 22 23:25 - 23:34 (00:08)
mee pts/0 :0.0 Sat Jul 22 23:18 - 23:34 (00:15)
mee console :0 Sat Jul 22 23:18 - 23:34 (00:15)
reboot system boot 6.4.3-1-default Sat Jul 22 23:18 - 23:34 (00:15)
mee pts/1 :0.0 Sat Jul 22 14:47 - 17:21 (02:33)
mee pts/0 :0.0 Sat Jul 22 14:47 - 17:21 (02:34)
Useless output of new last (wtmpdb):
mee tty7 :0 Sun Jul 23 05:01 - still logged in
mee tty7 :0 Sat Jul 22 23:18 - still logged in
mee tty7 :0 Sat Jul 22 14:47 - still logged in
mee tty7 :0 Sat Jul 22 13:44 - still logged in
mee tty7 :0 Sat Jul 22 06:48 - still logged in
mee tty7 :0 Fri Jul 21 23:52 - still logged in
mee tty7 :0 Fri Jul 21 16:21 - still logged in
mee tty7 :0 Fri Jul 21 12:42 - still logged in
mee tty7 :0 Fri Jul 21 06:51 - still logged in
mee tty7 :0 Thu Jul 20 23:32 - still logged in
To have 15 years to clean up and eliminate bugs instead of introducing new untested replacement at the last minute. To have time to catch external software using legacy interface and fix it.