-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-10-02 at 15:47 +0200, Daniel Bauer wrote:
Hm... when I typed ntptrace (as root) I got:
localhost: stratum 3, offset 0.002145, synch distance 0.974084 swisstime.ee.ethz.ch: stratum 2, offset 0.000051, synch distance 0.015953 129.132.2.22: timed out, nothing received ***Request timed out
So I thought, swisstime is too slow in answering, went to Yast, choosed another timeserver, but then ntptrace gave only: localhost: stratum 16, offset 0.000000, synch distance 0.000615
You should have more than one server to read the time from. A dozen or two would be apropiate. Enter several server lines like this: server pool.ntp.org server pool.ntp.org server pool.ntp.org server pool.ntp.org server es.pool.ntp.org server uk.pool.ntp.org server fr.pool.ntp.org server ch.pool.ntp.org
But var/log/messages still says
That's not the log file to look at - instead: logfile /var/log/ntp # alternate log file logconfig =all Example log: 2 Oct 14:53:39 ntpd[4601]: synchronized to 194.*.*.*, stratum 2 2 Oct 14:59:10 ntpd[4601]: time reset -0.799129 s 2 Oct 14:59:10 ntpd[4601]: system event 'event_clock_reset' (0x05) status 'leap_none, sync_unspec, 15 events, event_peer/strat_chg' (0xf4) 2 Oct 14:59:10 ntpd[4601]: system event 'event_peer/strat_chg' (0x04) status 'leap_none, sync_unspec, 15 events, event_clock_reset' (0xf5) 2 Oct 14:59:12 ntpd[4601]: peer 194.*.*.* event 'event_reach' (0x84) status 'unreach, conf, 4 events, event_reach' (0x8044) 2 Oct 14:59:15 ntpd[4601]: peer 195.*.*.* event 'event_reach' (0x84) status 'unreach, conf, 4 events, event_reach' (0x8044) 2 Oct 14:59:22 ntpd[4601]: synchronized to 194.*.*.*, stratum 2 2 Oct 15:00:12 ntpd[4601]: peer LOCAL(0) event 'event_reach' (0x84) status 'unreach, conf, 4 events, event_reach' (0x8044) 2 Oct 15:00:14 ntpd[4601]: peer 193.*.*.* event 'event_reach' (0x84) status 'unreach, conf, 4 events, event_reach' (0x8044) 2 Oct 15:00:14 ntpd[4601]: peer 194.*.*.* event 'event_reach' (0x84) status 'unreach, conf, 4 events, event_reach' (0x8044) 2 Oct 15:00:16 ntpd[4601]: peer 213.*.*.* event 'event_reach' (0x84) status 'unreach, conf, 4 events, event_reach' (0x8044) 2 Oct 15:00:19 ntpd[4601]: offset -0.016159 sec freq 4.865 ppm error 0.008658 poll 6 2 Oct 15:44:19 ntpd[4601]: synchronized to 193.*.*.*, stratum 2 2 Oct 16:00:19 ntpd[4601]: offset 0.013454 sec freq 3.475 ppm error 0.048369 poll 8 localhost: stratum 3, offset 0.005532, synch distance 0.167255 193.*.*.*: stratum 2, offset 0.000921, synch distance 0.085274 *.*.es: stratum 1, offset 0.000000, synch distance 0.000537, refid 'GPS'
Anyway I still would like to find out, if, when and how many times this deamon will check my time,
Good luck! It does it when it wants to do it :-)
but all those messages are really cryptic to me.
So they are :-P
I even don't know what "stratum" means. When I was younger, there was a disco here called "stratos" :-)
Have a look at "http://www.ntp.org/". Or install package "xntp-doc" and read it. "Stratum" tells the level in the ntp server chain. Stratum 1 is a server with a direct connection to a precise clock, like a GPS card, a special radio, or one of the atomic clocks mantained by some labs. We, as users, should not request the time form them, but use level 2 or 3 instead (however, if they are in the pool, that's their fault). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFIR5htTMYHG2NR9URAs7DAJ9hjvAUzYDPcuEXy3ApY5ubi0wv/QCfQt+c HvSWjtg0SsP5YHVTC5hnMm0= =jTV7 -----END PGP SIGNATURE-----