|
#1
|
||||
|
||||
|
My provider does not send NITZ information.
I was looking for a way to synchronize my N900 time with the DCF77 time from my desktop machine (I use some older parallel port dongle, see also http://de.wikipedia.org/wiki/DCF77 ). There are only some posts about some older version of "rdate", about a daemon "openntpd" (I do not want to install a complete ntp daemon, I only need the client). Finally I found this website: http://home.mminternet.com/delaroca/index.html/ where there is: "Download ntpdate.gz: Ntpdate 4.2.6p1. Home (Install in your favorite bin/ dir, run in root)". Installed this and now I can either do (after starting the ntp daemon on my desktop) ntpdate <my desktop in my WLAN> or switch on internet and ntpdate <public ntp server> hwclock -w also works.
|
|
#2
|
|||
|
|||
|
Oh! Interesting, how it is possible for telephone provider to do not send timing info... Very intriguing.
How you find out what provider doesn't send clock info? |
|
#3
|
|||
|
|||
|
I just wonder why no-one has written a small daemon to get the time from the GPS at intervals. E.g., using this as a time source in ntpd ...
I will try and write a small app for this in Qt first ... I've been wondering why no-one has done this since the release of the N95 ... |
|
#4
|
||||
|
||||
|
Quote:
That simple. ;-) NITZ would be better but ntpdate is a workaround. |
|
#5
|
|||
|
|||
|
Quote:
Having an ntpd daemon running periodically and only when there is a network connection (it should never initiate a connection) would be great. Perhaps there is a way to hook it into the network up scripts? |
|
#6
|
||||
|
|
||||
|
I would suggest people use pool.ntp.org for their timing needs : )
|
|
#7
|
||||
|
||||
|
Quote:
pool.ntp.org does not work in Austria. It results in "# Willkommen # auf dem Österreichischen Jugendportal" There seems to be a tiny DNS problem. ;-) You have to use http://www.pool.ntp.org/ |
![]() |
|
|