> > OK. I asked since a timewarp of 200ms is a bit surprising for > > real HW, but is something to be expected if you were running in a > > VM.
> The following is an example from ntpd.log > 14 Apr 07:22:25 ntpd[1048]: synchronized to 10.0.0.5, stratum 1 > 14 Apr 07:22:25 ntpd[1048]: time reset +0.231004 s > 14 Apr 07:23:35 ntpd[1048]: synchronized to 10.0.0.5, stratum 1 > 14 Apr 07:39:33 ntpd[1048]: time reset +0.318457 s > 14 Apr 07:39:33 ntpd[1048]: kernel time sync disabled 0041 I suspect one of the next questions will be to know more about the system "10.0.0.5," and to see the output of ntpq -p on the system from which the ntpd.log snippet comes. rick jones -- No need to believe in either side, or any side. There is no cause. There's only yourself. The belief is in your own precision. - Joubert these opinions are mine, all mine; HP might not want them anyway... :) feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH... _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
