(RADIATOR) after year 2037

[Dave Kitabjian]

Yea, but what if the customer has already paid for 40 years up front and
so his expriation date is 2040?

Dave
:) sorry, couldn't resist

> -----Original Message-----
> From: jlewis at lewis.org [mailto:jlewis at lewis.org] 
> Sent: Wednesday, November 14, 2001 9:37 AM
> To: ISMAIL,IRWAN (HP-Malaysia,ex1)
> Cc: radiator at open.com.au
> Subject: Re: (RADIATOR) after year 2037
> 
> 
> On Wed, 14 Nov 2001, ISMAIL,IRWAN (HP-Malaysia,ex1) wrote:
> 
> > Hi,
> >
> > I tried switching the date on my NT server (which is 
> running radiator) 
> > to a date that is after year 2037 and I would get a "no reply" if I 
> > tried to authenticate. Is this a limitation of Radiator? 
> The logfile 
> > would also be saved as 1900-MM-DD, instead of 20XX-MM-DD.
> 
> How far after 2037 were you trying to go?  32-bit systems 
> using signed 32-bit int's to store "unix time" as seconds 
> since 1970 have a problem trying to deal with times after Jan 
> 18, 2038.  Hopefully, by that time, there won't be any 32-bit 
> CPU's kicking around.
> 
> -- 
> ----------------------------------------------------------------------
>  Jon Lewis *jlewis at lewis.org*|  I route
>  System Administrator        |  therefore you are
>  Atlantic Net                |
> _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
> 
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.
> 
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.