On Thu, 15 Dec 2005 16:23:20 -0800, Ted Unangst wrote: > start it with -s.
Ted, thanks, I know. But this doesn't help my concerns: 1. Since it isn't the default flag; plus I *did* use it on those Proliants and the drift increasingly moved away from 0. Or, as we say in Process Control, the Error increased continuously. While a controller ought to converge it to zero. In summary: the controller does not notice and subsequently not warn when it runs off. Any reasonable controller has a characteristic adopting to the size of the error, btw. 2. Since it isn't the default flag, it can literally take ages (even on a non-Proliant) to reach the correct time. It keeps the user in a false sense of security. As much as I welcomed openntpd (the other one is a bore to set up), now I feel less happy. I don't need more than 50 msec of precision, but I'd sleep better if it noticed 'running away'; and I'd be happy if it noticed great deviations and warned me, respectively initiated some rough setting (what -s does) on its own. 2 sen, Uwe
