On Monday 02 October 2006 09:47, Daniel Bauer wrote:
Anyway I still would like to find out, if, when and how many times this deamon will check my time...
Hi Daniel, From one of my previous posts on SLE:
From my not always perfect memory:
When you first set your system up as an ntp client, the script(s) accomplish the following:
1. determines the latency between the two systems, i.e. requests the time from the ntp server N times over the course of Y period, calculates the latencies and uses the average in later calculations.
2. with the average latency measured, it again requests the current time from the ntp server and adjusts the received time for latency. With the "true" time known, it then determines if the client is "fast" or "slow" and by how much.
3. it then calculates a series of small, incremental adjustments designed to gently "nudge" the client system into sync with the server without disrupting time sensitive processes and data.
4. When the above process is completed, the client is effectively synced to the server. This makes two things possible: a) the hardware clock drift can be accurately measured and, b) that drift can be compensated for in software until the hardware clock is next set.
Now, I could be "all wet" but this is how I understand the overall design of the process.
1. YaST -> System -> System Services (Runlevel) let the list refresh. 2. Select 'Expert' mode and 'stop' SuSEFirewall2 phase 2 only (not "disable"... use the start/stop/refresh drop-down control) (this temporarily 'drops' the firewall) 3. Leave above window open, open Network Services -> NTP Client 4. Enter the time server by name, not IP, and test. 5. If the test succeeds, click "OK" or "Done" or "Finish" (whatever is
From another of my past SLE posts... I believe this applies as you're running 10.0, correct?: there)
6. If the test fails, try another. Repeat until the test succeeds. 7. Start SuSEFirewall2 phase 2 again to bring the firewall back up. 8. select "Done" or "Finish" or "OK" and close YaST
My understanding is you really only want to sync to *one* known reliable server (or pool) because the syncing process is just that: a process which takes time to complete. This is how I set my 10.0 system up immediately following installation and it's been a real "set and forget" arrangement. hth & regards, Carl