Just an update, we have CSCse91635 filed for this issue. This will be
fixed in the next maintenance release.
Thanks
-Alok

> -----Original Message-----
> From: Perfigo SecureSmart and CleanMachines Discussion List 
> [mailto:[log in to unmask]] On Behalf Of Alok 
> Agrawal (alagrawa)
> Sent: Wednesday, August 09, 2006 1:41 PM
> To: [log in to unmask]
> Subject: Re: Time configuration on 4.0.2
> 
> Hi Michael,
> Please can you tell me what code did you upgrade from? Did 
> you do the Inplace upgrade?
> Thanks
> -Alok
> 
> > -----Original Message-----
> > From: Perfigo SecureSmart and CleanMachines Discussion List 
> > [mailto:[log in to unmask]] On Behalf Of Michael Grinnell
> > Sent: Wednesday, August 09, 2006 1:31 PM
> > To: [log in to unmask]
> > Subject: Time configuration on 4.0.2
> > 
> > So we upgraded to 4.0.2 last night, and everything went 
> pretty well, 
> > but I noticed that the timestamp on our logs was off.  A 
> little poking 
> > around found that the timezone was set to PDT (America/
> > Vancouver) and while our system time was correctly set to 
> EDT (via the 
> > 'date' command) the hardware time kept getting reset to 
> several hours 
> > in the past (hwclock --show).  I'm not sure what the official Cisco 
> > fix for this is, but I ran 'timeconfig' from the command prompt and 
> > just chose the right timezone there.  That seems to have fixed it.
> > 
> > Michael Grinnell
> > Network Security Administrator
> > The American University
> > 
>