Garl, Thanks for the older Redhat fix. I was just going to look into that today.
Thanks, -Miller On 2/22/07, Garl Grigsby <[EMAIL PROTECTED]> wrote:
> Thanks Garl... NP. > > This looks very very similar to what I tried the other day and I got > my machine's time all fubar... the 'w' command would show a time 8 > hour sin the future, system clock showed current time... messing > around with them just made it worse... luckily I had backed up > /etc/locatime and could recover.. > > Followed the above verbatim and have the same problem.... the only > thing w/ correct lines are /America/Los_Angeles If that is the case then you have your hardware clock set to localtime instead of UTC. The common wisdom is to always set your hardware clock to UTC. Then let the system set the software clock based on PST8DST. So, in your case instead of symlinking to PST8DST, symlink to '../America/Los_Angeles'. > > Again, glad I had a backup.... Alternately you can do the following: 1) Update the TZ data files using the procedure I sent earlier. 2) run the timeconfig command and make sure the UTC setting is correct. If you want to switch the hardware clock to UTC do so now. We will adjust shortly. 3) Select the correct timezone, 'America/Los_Angeles' and exit. 4) This should create the correct localtime file. (keep your backup just in case). 5) Then check the system clock. If it is off, and it might be (esp if you switched to UTC), sync your clock to some known source (i.e. run 'ntpdate time.nist.gov') 6) Check the time. If it is correct, sync your hardware clock to the software clock using 'hwclock --systohc'. Garl Garl _______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
_______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
