On Thu, Sep 05, 2002 at 10:30:23PM -0400, Patrick Wiseman wrote: > On 6 Sep 2002, Dan Jacobson wrote: > > > $ touch -t 200011111111 a > > $ touch -t 201111111111 a > > $ touch -t 211111111111 a > > touch: invalid date format `211111111111' > > > > Oh great, can't deal with dates in the next century. Hope this isn't > > a deep routed problem for all of Unix or something. > > 2038 is when our dates run out: > > # touch -t 203711111111 a > # touch -t 203811111111 a > touch: invalid date format `203811111111' > > I believe it's supposed to be "automagically" fixed when we move from 32 > to 64 bits of something or other :) > > (Can anyone confirm this impression I have?) > I believe this is the case as the 2038 limit is based on the fact the largest 32 bit number which can be used for the unixtimestamp just happens to be that year... Which I believe should be 2038-01-18 19:14:07 or in unix timestamp format 2147483647... Jeremy
Attachment:
pgp1WrhHqJ4Qp.pgp
Description: PGP signature