diff options
author | Denys Vlasenko <vda.linux@googlemail.com> | 2019-10-30 12:13:46 +0100 |
---|---|---|
committer | Denys Vlasenko <vda.linux@googlemail.com> | 2019-10-30 12:18:07 +0100 |
commit | ea096d6c1389c93bdb6c6c45a04aff9062c7d8cf (patch) | |
tree | 509ec77841766251b090e145d7435c4688cf0762 /libbb/missing_syscalls.c | |
parent | 6b4960155e94076bf25518e4e268a7a5f849308e (diff) | |
download | busybox-ea096d6c1389c93bdb6c6c45a04aff9062c7d8cf.tar.gz |
ntpd: decrease MIN_FREQHOLD by 2, increase "penalty" for largish offset x2
> 2018-07-25:
> ntpd: increase MIN_FREQHOLD by 3
> This means we'll start correcting frequency ~5 minutes after start,
> not ~3.5 ones.
> With previous settings I still often see largish ~0.7s initial offsets
> only about 1/2 corrected before frequency correction kicks in,
> resulting in ~200ppm "correction" which is then slowly undone.
Review of real-world results of the above shows that with small
initial offsets, freq correction can be allowed to kick in sooner,
whereas with large (~0.8s) offsets, we still start freq correction
a bit too soon.
Let's rebalance this a bit.
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'libbb/missing_syscalls.c')
0 files changed, 0 insertions, 0 deletions