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)
On 17/06/13 05:40, Mario Frasca 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 ne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 ne
3 matches
Mail list logo
