Hi, as already told ;), wtmp has a Y2038 problem which the glibc developers don't plan to fix, but instead they want deprecate that API. (For background see https://www.thkukuk.de/blog/Y2038_glibc_wtmp_64bit/) On openSUSE Tumbleweed/MicroOS/... we introduced meanwhile wtmpdb, which solves the Y2038 problem and some others, too. "wtmpdb last" should work already today and show you similar output compared with "last" itself. The next and final step will be, making "last" a link to "wtmpdb last" and rename the old last to "last.legacy". There are currently no plans to disable writing of wtmp entries completly, I expect that this will come most likely together with utmp. So the applications reading wtmp directly (currently I'm only aware of accounts-daemon, maybe samba, haven't analyzed that code yet) should continue to work. The other 99% of applications accessing wtmp do only create new entries, this should cause no issues. But: due to a one year old bug in systemd-presets-common-SUSE, the service files didn't got always enabled. IMPORTANT: please check that the wtmpdb-update-boot.service and wtmpdb-rotate.timer are enabled, if not, please enable them: systemctl enable --now wtmpdb-update-boot.service systemctl enable wtmpdb-rotate.timer This is only necessary if you did updates, not for systems which got fresh installed this week. Thanks, 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)