OK, but i think this is bug and it may be solved.
When ntpd -S says adjusting local clock by 3601.017312s
adjtime failed: Invalid argument
What about to call something like:
int ntpd_adjtime(double d)
....
&tv=max(&tv,ADJTIME_MAX);
if (adjtime(max(&tv), &olddelta) == -1)
log_warn("adjtime failed");
return (synced);
}
Or report it as bug in adjtime?
On Mon, 17 Jun 2013 10:40:58 +0200 Mario Frasca <[email protected]> wrote:
> the main problem with this bug is that you can't start 'ntpd' if the
> time is not set approximatively correct from the start. take for
> example a computer without memory of the outside time (for example
> because its battery is faulty), then you somehow need bootstrap the
> procedure and chances are that you do not want to do this by hand.
>
> if you install 'ntpdate' and run it before 'ntpd' starts, things
> should go fine.
>
>
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
