Re: 64-bit time_t and __WORDSIZE_TIME64_COMPAT32

[Thorsten Kukuk <kukuk@suse.com>]

On Wed, Feb 08, Andreas Schwab wrote:

> On Feb 08 2023, Thorsten Kukuk via Libc-alpha wrote:
> 
> > That's solveable with e.g. creating a new name for them (.e.g
> > /run/utmp64 instead of /run/utmp)
> 
> That needs to be coordinated with all consumers and producers of those
> files.

If the consumers and producers uses the glibc API for this, you just
need to recompile them with the new interface. No need to change any 
paths in the source code, the fitting ones comes with glibc, too.

If they declare utmp and the file locations at their own, you need to
modify them anyways. And if you do that, you can change them to use
the official glibc API and not their own written one.

But at least it's a solution to solve the Y2038 problem in glibc for
64bit architectures like x86-64.

And for utmp you can ignore the on disk file format anyways, at it will
not survive a reboot. Not sure about lastlog, wtmp is a problem.

  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)