Hi All,
Whenever I reboot my Fedora 10 machine, the system time jumps to current time + 05:30. Looks time it is jumping by timezone offset IST (GMT+ 5:30). The hardware clock has the correct time after reboot though. I am not using the UTC clock option. Link '/etc/localtime' points to the correct timezone file and file /etc/sysconfig/clock also contains the correct timezone.
Any ideas, what might have gone wrong?
Thanks, Anoop
Anoop wrote:
Hi All,
Whenever I reboot my Fedora 10 machine, the system time jumps to current time + 05:30. Looks time it is jumping by timezone offset IST (GMT+ 5:30). The hardware clock has the correct time after reboot though. I am not using the UTC clock option. Link '/etc/localtime' points to the correct timezone file and file /etc/sysconfig/clock also contains the correct timezone.
Any ideas, what might have gone wrong?
What do you mean by system time? I mean, what is displayed in GNOME/KDE applets or what you see with "date" or what...
Check (some things, you have already done...) the output of
date date -u hwclock hwclock -u
then have a look at
/etc/localtime /etc/sysconfig/clock /etc/adjtime
check if you have a TZ variable involved with
echo $TZ
and, are you running ntpd?
/etc/init.d/ntpd status
if yes, what does it say when you do
ntpq -p
These problems are often caused by something wrong in one place and "fixing" it in the wrong one is very easy.
Please consider switching to UTC for your hardware clock. It is better (I know, if you also boot Windows you can't).
I adventurously guess that you have a wrong timezone setting somewhere and running ntpdate on boot.
Best regards.
On Fri, Feb 6, 2009 at 7:01 PM, Roberto Ragusa mail@robertoragusa.it wrote:
Anoop wrote:
Hi All,
Whenever I reboot my Fedora 10 machine, the system time jumps to current time + 05:30. Looks time it is jumping by timezone offset IST (GMT+ 5:30). The hardware clock has the correct time after reboot though. I am not using the UTC clock option. Link '/etc/localtime' points to the correct timezone file and file /etc/sysconfig/clock also contains the correct timezone.
Any ideas, what might have gone wrong?
What do you mean by system time? I mean, what is displayed in GNOME/KDE applets or what you see with "date" or what...
Check (some things, you have already done...) the output of
date date -u hwclock hwclock -u
then have a look at
/etc/localtime
This was a soft link to '/usr/share/zoneinfo/Asia/Kolkata' on my machine. Then I looked on another machine (Fedora 9), there '/etc/localtime' was itself the 'Kolkota' time zone file. I copied /etc/localtime from fedora 9 to my machine and it worked. I am still not sure what was the issue though.
Thanks, Anoop
/etc/sysconfig/clock /etc/adjtime
check if you have a TZ variable involved with
echo $TZ
and, are you running ntpd?
/etc/init.d/ntpd status
if yes, what does it say when you do
ntpq -p
These problems are often caused by something wrong in one place and "fixing" it in the wrong one is very easy.
Please consider switching to UTC for your hardware clock. It is better (I know, if you also boot Windows you can't).
I adventurously guess that you have a wrong timezone setting somewhere and running ntpdate on boot.
Best regards.
Roberto Ragusa mail at robertoragusa.it
Anoop wrote:
On Fri, Feb 6, 2009 at 7:01 PM, Roberto Ragusa mail@robertoragusa.it wrote:
/etc/localtime
This was a soft link to '/usr/share/zoneinfo/Asia/Kolkata' on my machine. Then I looked on another machine (Fedora 9), there '/etc/localtime' was itself the 'Kolkota' time zone file. I copied /etc/localtime from fedora 9 to my machine and it worked. I am still not sure what was the issue though.
Possible explanation: when the system tried to read the hw clock and set the system clock, it needed info about your timezone (because UTC=no) and tried to read /etc/localtime, which was a symlink to /usr, which was not mounted yet.
Do you have a separate /usr partition?
It seems reasonable to me.
Best regards.
On Fri, Feb 6, 2009 at 8:33 PM, Roberto Ragusa mail@robertoragusa.it wrote:
Anoop wrote:
On Fri, Feb 6, 2009 at 7:01 PM, Roberto Ragusa mail@robertoragusa.it wrote:
/etc/localtime
This was a soft link to '/usr/share/zoneinfo/Asia/Kolkata' on my machine. Then I looked on another machine (Fedora 9), there '/etc/localtime' was itself the 'Kolkota' time zone file. I copied /etc/localtime from fedora 9 to my machine and it worked. I am still not sure what was the issue though.
Possible explanation: when the system tried to read the hw clock and set the system clock, it needed info about your timezone (because UTC=no) and tried to read /etc/localtime, which was a symlink to /usr, which was not mounted yet.
Do you have a separate /usr partition?
Yes :). Thanks a lot.
-Anoop
It seems reasonable to me.
Best regards.
Roberto Ragusa mail at robertoragusa.it
-
Anoop -
Roberto Ragusa