Hello,

on a customer machine running Solaris 10 we encountered, that xntpd is continuously stepping time in alternating steps. An extract from syslog shows:
...
Mar 11 03:23:01 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 4.948524 s
Mar 11 03:27:39 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -4.974163 s
Mar 11 03:32:41 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 4.976014 s
Mar 11 03:37:19 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -4.983586 s
Mar 11 03:42:21 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 5.208262 s
Mar 11 03:47:00 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -5.222916 s
Mar 11 03:52:02 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 5.405276 s
Mar 11 03:56:40 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -5.427286 s
Mar 11 04:01:43 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 5.573209 s
Mar 11 04:06:21 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -5.579299 s
Mar 11 04:11:24 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 5.584294 s
Mar 11 04:16:02 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -5.577298 s
Mar 11 04:21:06 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 5.654892 s
Mar 11 04:25:43 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -5.546643 s
Mar 11 04:30:46 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 5.552552 s
Mar 11 04:35:24 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -5.551743 s
Mar 11 04:40:28 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 5.784310 s
Mar 11 04:45:05 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -5.797694 s
Mar 11 04:50:09 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 6.161179 s
Mar 11 04:54:47 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -6.169695 s
Mar 11 04:59:51 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 6.206629 s
Mar 11 05:04:29 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -6.215884 s
Mar 11 05:09:33 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 6.255373 s
Mar 11 05:14:11 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -6.288433 s
Mar 11 05:19:15 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 6.356196 s
Mar 11 05:23:53 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -6.367971 s
Mar 11 05:28:57 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 6.325430 s
Mar 11 05:33:35 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -6.322147 s
Mar 11 05:38:39 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 6.434979 s
Mar 11 05:43:16 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -6.427836 s
Mar 11 05:48:21 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 6.437011 s
Mar 11 05:52:58 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) -6.467908 s
Mar 11 05:58:03 antares xntpd[527]: [ID 774427 daemon.notice] time reset (step) 6.498646 s
...

What could be the reason for this behaviour?

I have to mention, that we are not really familiar with NTP, we only provide a JAVA enterprise application, which had a serious problem with the time steps. Therefore we deactivated xntpd, but this can only be a temporary workaround.

Thank you for any ideas.
Hounce