Re: Y2K rollover Vigilance

["Alejandro Rusell" <arusel () mecon ar>]

Having checked all out, what do you think of turning the date back, say, 28 years
in the past, just in case.  Do you all wizards know of any 72year 
problem?.   Seeing that the day's configurations is the same every 
28 years, we think that all systems that don't depend of the actual 
date should be moved back.  After the rollover period (which we 
extend up to first days of March), all we have to do is modify the 
year part of the date in the logs for our processing (ie: 1971 = 
1999, 1972 = 2000).

We are thinking of doing it in routers and such devices.  

We have already tested that the devices support such an old date.

Any suggestions are welcome.

Regards,

A. J. Rusell
Data Networks Consultant

> > I would like to get the wizards' take on what people are doing 
with respect
> > to staying connected and functional on the Internet during the rollover to
> > the year 2000.  Do most organizations seem to be leaning towards reduced
> > exposure (i.e. shutting down incoming SMTP, restricting download cpability,
> > etc.), total blackout, or business as usual.
>
> If one is doubt of the Y2k compliance of their webservers, mailservers,
> routers, and firewalls, he/she should have done their homework by now.
>
> All machines should have been taken off-air and had their clocks changed to
> pre-Y2K, watch the rollover to check for any problems, reset the clocks to the
> real time, and put back all machines on-line. This, of cource, should have
> been done months ago.
>
> Firewalls are generaly new products, and wont have Y2k rollover problems. Most
> people run webservers that are fairly new too. Routers should have been
> checked long ago.
>
> If everything has been tested before to be Y2k-okay, then I see no reason to
> reduce exposure or shut things off.