On May 30, 2006, at 4:58 AM, Hubert Feyrer wrote:
> On Mon, 29 May 2006, Chuck Swiger wrote:
>> If the clock is far enough off that it needs to step the time by  
>> setting it, rather than using adjtime(), running at a high  
>> securelevel will prevent ntpd from doing so.  Reboot the system  
>> with a lower securelevel until the clock is synced, and then try  
>> again at a higher securelevel.
>
> hrm, shouldn't ntpdate take care of that, upon boot?

Yeah, if ntpdate runs before the securelevel gets elevated...?

>> It's possible the -x flag to ntpd will help, too....
>
> I'll try that one, so far it looks promising.
> Thanks!

You're welcome.  Just try to get the clock synced reasonably close  
before trying "-x", or else it may take an excessive amount of time  
to get synced using adjtime()...

-- 
-Chuck