Re: 64-bit time_t and __WORDSIZE_TIME64_COMPAT32

[Thorsten Kukuk <kukuk@suse.com>]

Hi,

to give a short update on this:

lastlog: see https://www.thkukuk.de/blog/Y2038_glibc_lastlog_64bit/

openSUSE Tumbleweed and MicroOS use already lastlog2, we are starting now
to remove the "old" lastlog code and usage. ALP is currently switching
to it.


wtmp: see https://www.thkukuk.de/blog/Y2038_glibc_wtmp_64bit/

Even if many applications write wtmp entries in a chaotic or wrong way,
there is only one application from relevance reading it: last.
lslogins reads it, too, don't know how often it is really used. adjtimex
reads it, too, but I haven't found any application writing this type of
entries adjtimex tries to read.

wtmpdb is currently in security review, afterwards we will switch to it,
too. Everything is already prepared for this.


utmp: see https://www.thkukuk.de/blog/Y2038_glibc_utmp_64bit/

systemd accepted the necessary patches, v254 should contain them. First
upstream projects accepted the necessary adjustements, too. 
Main usage of utmp is to find out how many users are logged in, else
there are wall, write, who and w.
For coreutils patches exist beside who, procps accepted already the
first bunch, util-linux has open PRs for the next release, Linux-PAM
accpeted them, too. Will be in the next release the coming days.

Only problem is openssh, since they know the TTY only after PAM
authentication and systemd-logind has no interface to adjust the TTY
later. I will look into this next.

So from my point of view, dropping lastlog and wtmp should be straight
forward, utmp will need quite some more work.

  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)