Re: [chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 2.1.1-89-g3cd32ed |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
commit 1b2510e4b260eed2e7fef9e539cd031bd89898c9
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date: Tue Sep 15 15:24:28 2015 +0200
sys_linux: use timex driver
Remove functions that are included in the new timex driver. Keep only
functions that have extended functionality, i.e. read and set the
frequency using the timex tick field and apply step offset with
ADJ_SETOFFSET.
Merge the code from wrap_adjtimex.c that is still needed with
sys_linux.c and remove the file.
commit e735be59a7d6077414244d2c54fcabb736e0f3ff
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date: Tue Sep 15 15:03:37 2015 +0200
sys: add generic timex driver
This is based on sys_linux.c and wrap_adjtimex.c. It's intended for all
systems that support the adjtimex() or ntp_adjtime() system call. The
driver functions can be replaced with extended system-specific versions
(e.g. to control the frequency with the tick field on Linux).
commit 5190539ce1efe0a9fc14e2197017f8cb4bb6f0e6
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date: Thu Sep 10 15:34:56 2015 +0200
test: add tests for system adjtime() and ntp_adjtime()
Include a test program to determine how the adjtime() implementation
behaves. Check the range of supported offset, support for readonly
operation, and slew rate with different update intervals and offsets.
Also, add a test for ntp_adjtime() to check what frequency range it
supports.
I am not sure what the consequences of this are, but if it limits chronyd on
Linux to 500PPM adjustment, it is a real step back. One of the advantages of
chrony has always been that it could rapidly adjust the time by slewing, since
it could slew up to a rate of 1/10. (ten seconds to slew a second) and could
remove the coarse adjustment of the rate ( so if you clock was out by 300PPM
on average, it could still use the full 500PPM adjustment width of the fine
control. ) To go the silly ntpd rate limits of just 500PPM is to me a major
change in chrony and to me a backward step. Of course I may be misinterpreting
this.
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.