More information now:

1) It seems to be rolling the clock back an hour every hour at 7 minutes
past
2) It all started on April 9th between 07:10 and 07:15 GMT, at which time
the system clock jumped backward two weeks to the minute. So the clock
suddenly went from April 9th at 07:10GMT to March 26 07:10GMT. (the exact
time unknown but between 07:10 and 07:15 GMT).
3) After that big jump back, the clock resets itself every hour at 7 minutes
past, as illustrated in this excerpt from the cron log:

> CMD: /usr/lib/sa/sa1 sys 2499 c Sun Apr 9 06:35:00 2006
< sys 2499 c Sun Apr 9 06:35:00 2006
> CMD: /usr/lib/sa/sa1 sys 2591 c Sun Apr 9 06:40:00 2006
< sys 2591 c Sun Apr 9 06:40:01 2006
> CMD: /usr/lib/sa/sa1 sys 2620 c Sun Apr 9 06:45:00 2006
< sys 2620 c Sun Apr 9 06:45:00 2006
> CMD: /usr/lib/sa/sa1 sys 2708 c Sun Apr 9 06:50:00 2006
< sys 2708 c Sun Apr 9 06:50:00 2006
> CMD: /usr/lib/sa/sa1 sys 2817 c Sun Apr 9 06:55:00 2006
< sys 2817 c Sun Apr 9 06:55:00 2006
> CMD: /usr/lib/sa/sa1 sys 2911 c Sun Apr 9 07:00:00 2006
< sys 2911 c Sun Apr 9 07:00:00 2006
> CMD: /usr/lib/sa/sa1 sys 2999 c Sun Apr 9 07:05:00 2006
< sys 2999 c Sun Apr 9 07:05:00 2006
> CMD: /usr/lib/sa/sa1 sys 3070 c Sun Apr 9 07:10:00 2006
< sys 3070 c Sun Apr 9 07:10:00 2006

SOMETHING HAPPENS HERE. THEN. YOU WILL NOTICE THAT THE SAR JOB AT 5 MINUTES
PAST THE HOUR IS THE LAST JOB THAT RUNS BEFORE THE CLOCK GOES BACK AN HOUR
AND IT REPEATS ITSELF, NO MATTER WHAT TIME.

> CMD: /usr/lib/sa/sa1 sys 3134 c Sun Mar 26 00:15:00 2006
< sys 3134 c Sun Mar 26 00:15:00 2006
> CMD: /usr/lib/sa/sa1 sys 3221 c Sun Mar 26 00:20:00 2006
< sys 3221 c Sun Mar 26 00:20:00 2006
> CMD: /usr/lib/sa/sa1 sys 3302 c Sun Mar 26 00:25:00 2006
< sys 3302 c Sun Mar 26 00:25:00 2006
> CMD: /usr/lib/sa/sa1 sys 3394 c Sun Mar 26 00:30:00 2006
< sys 3394 c Sun Mar 26 00:30:00 2006
> CMD: /usr/lib/sa/sa1 sys 3481 c Sun Mar 26 00:35:00 2006
< sys 3481 c Sun Mar 26 00:35:01 2006
> CMD: /usr/lib/sa/sa1 sys 3510 c Sun Mar 26 00:40:00 2006
< sys 3510 c Sun Mar 26 00:40:00 2006
> CMD: /usr/lib/sa/sa1 sys 3602 c Sun Mar 26 00:45:00 2006
< sys 3602 c Sun Mar 26 00:45:00 2006
> CMD: /usr/lib/sa/sa1 sys 3695 c Sun Mar 26 00:50:00 2006
< sys 3695 c Sun Mar 26 00:50:00 2006
> CMD: /usr/lib/sa/sa1 sys 3777 c Sun Mar 26 00:55:00 2006
< sys 3777 c Sun Mar 26 00:55:00 2006
> CMD: /usr/lib/sa/sa1 sys 3869 c Sun Mar 26 01:00:00 2006
< sys 3869 c Sun Mar 26 01:00:00 2006
> CMD: /usr/lib/sa/sa1 sys 3929 c Sun Mar 26 01:05:00 2006
< sys 3929 c Sun Mar 26 01:05:00 2006
> CMD: /usr/lib/sa/sa1 sys 3995 c Sun Mar 26 00:10:00 2006 CMD:
> /export/home/dallasadm/DoChk.ksh 1>/dev/null 2>&1 root 3996 c Sun Mar 26
> 00:10:00 2006
< sys 3995 c Sun Mar 26 00:10:00 2006
< root 3996 c Sun Mar 26 00:10:01 2006
> CMD: /usr/lib/sa/sa1 sys 4266 c Sun Mar 26 00:15:00 2006
< sys 4266 c Sun Mar 26 00:15:00 2006
> CMD: /usr/lib/sa/sa1 sys 4349 c Sun Mar 26 00:20:00 2006
< sys 4349 c Sun Mar 26 00:20:00 2006
> CMD: /usr/lib/sa/sa1 sys 4443 c Sun Mar 26 00:25:01 2006


"Terry" <terryfranklin@sbcglobal.net> wrote in message
news:b9a%f.67896$Jd.14456@newssvr25.news.prodigy.n et...
> Hello
>
> I have a 1280 running Solaris 8 and in the last few days, we have noticed
> that the clock seems to be losing an hour sporadically. I shut down ntp
> and the issue still occurs, and ntpdate functions correctly. But even with
> NTP off, the issue still happens.
>
> The system is set to GMT per /etc/default/init. I see no scheduled jobs
> that would affect the date.
>
> I did a for loop every 3 minutes running the date command (ntp is off at
> this point) and here is the last series I saw:
>
> Wed Apr 12 16:00:14 GMT 2006
> Wed Apr 12 16:03:14 GMT 2006
> Wed Apr 12 16:06:14 GMT 2006
> Wed Apr 12 15:09:14 GMT 2006
> Wed Apr 12 15:12:14 GMT 2006
> Wed Apr 12 15:15:14 GMT 2006
>
> I am continuing to monitor to see if it happens consistantly after a
> period of time, but wanted to see if anyone had any suggestions.
>
> Thanks
> Terry
>