> >If the sequence > # hwclock --hctosys > # date >shows the correct time, then > delay some time > # date >shows an incorrect time, then the issue is that something else >is skewing the system time after the initial sequence has been run. > >My guess is you're running ntpdate or rtime from a cron job or >something, that's getting the time from another machine and >setting the local clock. >
Yeah, I used ntpdate to set the time initially but ntpd is not running and I don't see it happening anywhere else (cron, init, etc). Looks like it was /etc/adjtime that was causing the skew (is that possible?). Blowing it away and letting it recreate it has cleared things up as the /etc/adjtime values before: -1714.782194 1055295468 0.000000 Were very different than after: 0.000000 1055296402 0.000000 I s'pose I should man hwclock and actually read rather than skim (cause it explains all this very well, doh!) ... But what would be the fun in that! Thanks for all the help! august -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
