|
2010-11-09
, 00:29
|
Posts: 992 |
Thanked: 995 times |
Joined on Dec 2009
@ California
|
#2
|
|
2010-11-09
, 12:48
|
Posts: 196 |
Thanked: 224 times |
Joined on Sep 2010
@ Africa
|
#3
|
|
2010-11-12
, 09:11
|
|
Posts: 168 |
Thanked: 58 times |
Joined on Aug 2010
@ Vienna
|
#4
|
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?
|
2010-11-28
, 00:05
|
Posts: 3,401 |
Thanked: 1,255 times |
Joined on Nov 2005
@ London, UK
|
#5
|
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?
|
2010-11-28
, 00:39
|
|
Posts: 549 |
Thanked: 299 times |
Joined on Jun 2010
@ Australian in the Philippines
|
#6
|
|
2010-11-29
, 17:06
|
|
Posts: 168 |
Thanked: 58 times |
Joined on Aug 2010
@ Vienna
|
#7
|
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.