64-bit time_t and __WORDSIZE_TIME64_COMPAT32

[Thorsten Kukuk]

Hi,

Currently on 64bit architectures like x86-64 we define 
__WORDSIZE_TIME64_COMPAT32 as 1, which leads to a 32bit time_t in utmp,
wtmp, lastlog and similar files.

This leads to the problem, that utmp, wtmp and lastlog stops working
in 2038 even if you have a pure 64bit system. 

Since I couldn't found anything about this, was it ever discussed or is
there any plan how to handle this?

Looking at my system there are much more systems using this interface
than I thought, so my first idea of just deprecating this interface is
no solution.

I think the only solution would be additional functions like for other
32bit time_t functions and use symbol versioning for it?

  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)