You are not logged in.
Pages: 1
Hi my clock goes out of sync all of the time. I've tried the openntpd thing from the arch wiki and I've gotten it to work. Howver, this doesn't last long before it goes out of sync again even when the daemon starts. I live in the Pacific time zone. Could someone please help me get this problem sorted out? I just need my clock to stay in sync.
Last edited by jimlikessweets (2010-01-27 06:00:15)
Offline
Same problem here!!!1
I'm tired of setting up the clock everytime i start the openntpd daemon. And i was trying a lot of ways to do it, but all fails when i reboot.
arst
Offline
Is it your bios clock that is slow or the system clock (whilst in linux)
if you run hwclock -s does it correct the time
Offline
Is it your bios clock that is slow or the system clock (whilst in linux)
if you run hwclock -s does it correct the time
No, nothing changes.
Offline
Then there is probably not much you can do if openntpd isn't working for you
How old is the computer? maybe the bios battery is running flat
Offline
Then there is probably not much you can do if openntpd isn't working for you
How old is the computer? maybe the bios battery is running flat
its an eee pc 1000h about a year and a half old. windows and other linux distros have working clocks on this computer. why cant arch?
Offline
I use ntp instead of openntp. Does openntp include the user space programs ntpq or ntpdc?
If they do, you might try to see if they provide any insight as to what the problem may be.
For example, the ntpdc program provides a shell interface. help is available using ?<return>. The commands dmpeers, sysstats, kerninfo and iostats may be of help.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
That's strange, did you run hwclock -s as root or with sudo, if you go into the bios does the clock read right?
Edit: or you could run sudo hwclock to see what the bios clock reads
Last edited by guzz46 (2010-01-21 19:43:01)
Offline
That's strange, did you run hwclock -s as root or with sudo, if you go into the bios does the clock read right?
Edit: or you could run sudo hwclock to see what the bios clock reads
My hardware clock is off by a few hours. How do I go about fixing it?
Offline
guzz46 wrote:That's strange, did you run hwclock -s as root or with sudo, if you go into the bios does the clock read right?
Edit: or you could run sudo hwclock to see what the bios clock reads
My hardware clock is off by a few hours. How do I go about fixing it?
Protip: man <command> almost always tells you how to do <action xyz>.
For example, hwclock --set --date "<the date>"
The human being created civilization not because of willingness but of a need to be assimilated into higher orders of structure and meaning.
Offline
There is a routine check. What does your /var/lib/hwclock/adjtime contain? It should look somewhat like
bp:~$ cat /var/lib/hwclock/adjtime
0.026639 1264322994 0.000000
1264322994
UTC
where the "UTC" could read "LOCAL" if your system is set to local time.
The first field (0.026639 in this example) should be a rather low absolute value. It records the offset by which the clock will be adjusted at system start. If this is too high, try to delete the adjtime file, set your hwclock to the proper time and reboot the system. This will recreate the adjtime file, which you should check again.
This does not help in every case. But it does rule out some common clock error source.
To know or not to know ...
... the questions remain forever.
Offline
There is a routine check. What does your /var/lib/hwclock/adjtime contain? It should look somewhat like
bp:~$ cat /var/lib/hwclock/adjtime 0.026639 1264322994 0.000000 1264322994 UTC
where the "UTC" could read "LOCAL" if your system is set to local time.
The first field (0.026639 in this example) should be a rather low absolute value. It records the offset by which the clock will be adjusted at system start. If this is too high, try to delete the adjtime file, set your hwclock to the proper time and reboot the system. This will recreate the adjtime file, which you should check again.
This does not help in every case. But it does rule out some common clock error source.
thanks a lot
this tip was very helpful
Offline
Problem solved thanks to a little man reading. Thanks a lot everyone, for your help
Offline
^ What did you do exactly to solve the problem?
Offline
Pages: 1