SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
The gradual drift in error can be accounted for as follows:
a) The time server(s) are blocking your attempts to synchronise with their servers because you have not requested permission to do so.
b) The time server(s) are blocking your attempts to synchronise with their servers because the frequency of your time checks exceeds the frequency they require. That is, your time hacks occur too frequently, consuming bandwidth, so they are blocking you.
So, the thing to do would be to verify that you are not synchronising too often, and that you are not being blocked because you failed to notify them of your use of their service.
There may be other factors at work, but these are the factors that come to mind most readily.
Nono, you've missunderstood, nothing to do with ntp, the *time* is correct and ntp is syncing correctly but whenever you do a 'ps' the start times for the processes are in the future. Wouldn't matter what the time is, you shouldn't start a new process and see the start time in the future!
The times seem to advance ~10 minutes for every 50 days the server is up, a reboot sorts it.
I've since found the same thing happens on SuSE 9.1 but doesn't do it on redhat 9, I've not got a 10/10.1 box that's been up long enough to see if it also does it on those. :-/