|Re: [chrony-users] chrony-1.30-pre1 released|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
On Fri, Jun 06, 2014 at 07:12:30PM +0000, Chris Dore wrote:
> From: Miroslav Lichvar [mailto:mlichvar@xxxxxxxxxx]
> Sent: June-06-14 9:10 AM
> > * Add maxslewrate directive to set maximum allowed slew rate
> Awesome stuff! If I understand this correctly, I should be able to stop using my own patched version of chrony once 1.30 releases?
Yes and it should be now even better. You can set the limit to any
value (not just a number of ticks) and it's applied to all slews, not
just the fast slews that were used for offsets over 0.5 second. This
is possible with the new generic slewing driver.
> The patch you suggested for me:
> diff --git a/sys_linux.c b/sys_linux.c
> index 80c888e..b95ba4d 100644
> --- a/sys_linux.c
> +++ b/sys_linux.c
> @@ -979,7 +979,7 @@ get_version_specific_details(void)
> dshift_hz = (double)(1UL << shift_hz);
> basic_freq_scale = dshift_hz / dhz;
> nominal_tick = (1000000L + (hz/2))/hz; /* Mirror declaration in kernel */
> - slew_delta_tick = nominal_tick / 12;
> + slew_delta_tick = nominal_tick / 2500;
> max_tick_bias = nominal_tick / 10;
> tick_update_hz = hz;
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.