[ntp:questions] LOCL clock reachability not 377?

Rob nomail at example.com
Mon Aug 25 07:03:44 UTC 2014


Harlan Stenn <stenn at ntp.org> wrote:
> Rob writes:
>> Harlan Stenn <stenn at ntp.org> wrote:
>> > Rob writes:
>> >> Harlan Stenn <stenn at ntp.org> wrote:
>> >> > Rob,
>> >> >
>> >> > You have seen 'flag1' in the recent ntp-dev SHM driver documentation,
>> >> > right?
>> >> 
>> >> I have installed ntp-dev and as part of that also ntp-dev-doc, but
>> >> it is essentially empty (only an automatically generated changelog).
>> >
>> > It's in the source distribution, html/drivers/driver28.html
>> 
>> The Debian package is still at p448 but I downloaded the source tarball
>> to have a peek in it, and as far as I understand this change it is not
>> going to solve one of my current issues...
>> 
>> (maybe it could have if the fudge time2 could be specified in milliseconds?)
>
> All the time variables are fixed-point decimals in seconds - you should
> be able to say 0.001 to mean a millisecond (or -0.001 if you need to go
> the other direction).

Should.   But:

        if (pp->sloppyclockflag & CLK_FLAG1)
                up->max_delta = 0;
        else if (pp->fudgetime2 < 1. || pp->fudgetime2 > 86400.)
                up->max_delta = 4*3600;
        else
                up->max_delta = (time_t)floor(pp->fudgetime2 + 0.5);



More information about the questions mailing list