| View previous topic :: View next topic |
| Author |
Message |
shaumux
Veteran
Joined: 13 May 2005
Posts: 1013
Location: Hamburg
|
 Posted: Tue Apr 10, 2007 7:31 pm Post subject: Clock problem |
 |
|
Hi
I am getting this problem with gentoo
At boot up i get so many messages saying
| Code: | | The modification date of a file in your /etc/{ conf.d,init.d } or /etc/rc.conf is in the future |
I have my clock variable set to local in /etc/conf.d/clock and the TIMEZONE varible to Asia/Calcutta.
but still my hardware clock seems to be running behind the time on the gentoo os, i think that might be causing the problem but have no idea how to fix these
Plz help me here, iam totally lost here
Thnx |
|
| Back to top |
|
 |
user11
Tux's lil' helper
Joined: 25 Nov 2005
Posts: 149
|
| Posted: Tue Apr 10, 2007 8:15 pm Post subject: |
|
|
I guess you would like option CLOCK_SYSTOHC="yes" in conf.d/clock.
Also, I think your /etc/localtime must point to a proper timezone file.
It is also possible that your clock is ok but some files are 'in future' because you touched them when you had wrong date (for example, when you installed system).
Generally, there should be no problems if you have CLOCK_SYSTOHC=true and do not move your time too much. |
|
| Back to top |
|
|
BitJam
Advocate
Joined: 12 Aug 2003
Posts: 2513
Location: Silver City, NM
|
| Posted: Tue Apr 10, 2007 8:28 pm Post subject: |
|
|
| I also have this problem occasionally. I have CLOCK_SYSTOHC set to yes and I use ntpd to keep my clock accurate when the system is running. |
|
| Back to top |
|
|
shaumux
Veteran
Joined: 13 May 2005
Posts: 1013
Location: Hamburg
|
| Posted: Tue Apr 10, 2007 8:55 pm Post subject: |
|
|
Ok so i set
| Code: | | CLOCK_SYSTOHC="yes" |
and rebooted the problem is fixed and no more of those messages anymore and the system clock and hardware clock r synchronized
but the strange thing is that i again set it back to no after rebooting but i'm not getting those problem anymore, very starnge acording to
dunno wat was causing it. |
|
| Back to top |
|
|
BitJam
Advocate
Joined: 12 Aug 2003
Posts: 2513
Location: Silver City, NM
|
| Posted: Tue Apr 10, 2007 9:27 pm Post subject: |
|
|
| Maybe you only really needed to set the hardware clock once. Once it got set, it kept time close enough so that you no longer got the "future" errors. |
|
| Back to top |
|
|
shaumux
Veteran
Joined: 13 May 2005
Posts: 1013
Location: Hamburg
|
| Posted: Tue Apr 10, 2007 9:44 pm Post subject: |
|
|
But isn't it supposed to synchronize my hardware clock and system clock at startup,
I forgot to check before the problem was fixed but now it is doing it at startup so there should't have been problem in the first place or the scenario i can can think of is the scripts were not running correctly or at all due to future time problem, but who knows might have been something comepletely different. |
|
| Back to top |
|
|
slycordinator
Advocate
Joined: 31 Jan 2004
Posts: 3065
Location: Korea
|
| Posted: Tue Apr 10, 2007 10:57 pm Post subject: |
|
|
ntpd only sets the system clock.
Furthermore, lets say I install gentoo from a CD. If your timezone isn't set it looks at it like you have the GMT timezone. And so you edit your config files. Then when you reboot you get the timezone fixed to your actual timezone and let ntpd set the clock. If you live west of Greenwich then you could end up with your time being set to something earlier than it was set to before.
So the file system says you edited the files at, say, 23:00 (since it was 23:00 in Greenwich when you edited the file). But your system says "WTF?!?! It's only 20:00 right now" because your current time for the new timezone is 20:00. So it'll give you a message that some of the files were modified in the future. |
|
| Back to top |
|
|
|
Other Things Gentoo
