NTP should be started at system boot and left alone after that. In the
start script in rc2.d (or rc3.d or wherever you choose), stick a line in
before the daemon start like this:

   <path_to>/ntpdate -v stratum_1_server stratum_1_server

(yes, two stratum 1 servers). That sets the clock dead on and then you
start the daemon. I use two servers at Argonne National Laboratories
just because they're close. Pick a couple close to you.

I use three pool servers in ntp.conf. Once the daemon has synchronized
(based on delay, offset and jitter -- execute nptq -p and look), the
system clock is, more or less, continuously nudged to stay on time. You
should not see many entries in your log file, but if you do you need to
find some better pool servers. I use 0.pool.ntp.org, 1.pool.ntp.org and
2.pool.ntp.org (check the web site for the pool servers available in
your area).

You really need to look at the log every so often and deal with any
problems that might crop up (problems meaning try other external servers
if you have large values in the ntpq -p display). You really won't see
adjustments of seconds in the log -- if you do, you've got a problem to
solve.

If you're really serious, get a radio clock, hook it up to one of your
servers and use that one as your timeserver for the whole internal
network... There are some nice GPS clocks available.

david@smooth1.co.uk schrieb:

No, it was weeks/months later (after reboot).

Yes, this was done with 'ntpdate'.

Yes, NTP was changing (backwards) the time and cron has started the
same cronjobs a second time.
Maybe an another had have the same problem and knows, that a newer or
other cron daemon on solaris don't have this problem ?

Regards,
try_and_err