[chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 1.29.1-150-g8210be0

[git@xxxxxxxxxxxxx]

This is an automated email from git. It was enerated because a ref
change was pushed to the repository "chrony/chrony.git".

The branch, master has been updated
       via  8210be0f17429f8e396d09a5e92c9e0f8f8e751e (commit)
       via  f88a712d01597c44dd4ddbc195dc1480cc0d72c9 (commit)
       via  9cf78b974aec90b1d7b78b9db1a4da08cd5845fc (commit)
       via  3e1dc801b0d96e732b295c8a90383de56ac488f5 (commit)
      from  cf3c7b3bd69bfb9c1d06451927168067fb229f7b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 8210be0f17429f8e396d09a5e92c9e0f8f8e751e
Author: Tjalling Hattink <t.hattink@xxxxxxxx>
Date:   Thu May 22 11:25:00 2014 +0200

    refclock: honour leap second flag in the PPS refclock
    
    This patch fixes leap second handling for the PPS refclock. Without the
    patch the PPS refclock will always report LEAP_normal. But if a locked
    refclock (the SHM clock in my case) does report a leap state it should
    also be taken over by the PPS refclock, otherwise chrony will still use
    LEAP_normal when the PPS clock is used as reference source.
    
    The patch will copy the leap state from the refclock. In case the PPS
    clock is not specifically locked to another refclock it will take over
    the leap state from the local clock.
    
    I've tested this patch by simulating a leap second through the samples
    for the SHM clock, and with the patch you will see chrony properly jump
    forward or backward on the leap second. Without the patch it will not do
    this and the clock becomes desynchronized and no leap state is reported
    upstream to other NTP clients.
    
    Signed-off-by: Tjalling Hattink <t.hattink@xxxxxxxx>

commit f88a712d01597c44dd4ddbc195dc1480cc0d72c9
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Wed May 21 17:36:51 2014 +0200

    sys: use maximum timeout for offsets below minimum correction
    
    There is no need to try to correct offsets below the specified minimum
    (1 nanosecond), let the clock drift away after crossing zero offset and
    avoid unnecessary updates.

commit 9cf78b974aec90b1d7b78b9db1a4da08cd5845fc
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Wed May 21 16:23:30 2014 +0200

    conf: add option to set maximum slew rate
    
    With the generic driver, the maxslewrate directive sets the maximum
    frequency offset that the driver is allowed to use to slew the time. By
    default, it's set to 83333.333 (1/12). This is identical to what Linux
    fast slewing used to use.

commit 3e1dc801b0d96e732b295c8a90383de56ac488f5
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Wed May 21 12:08:10 2014 +0200

    conf: change default corrtimeratio to 3.0
    
    This improves the overall frequency accuracy of the clock at a slight
    cost in the time accuracy.

-----------------------------------------------------------------------

Summary of changes:
 chrony.texi.in |   41 ++++++++++++++++++++++++++++++-----------
 conf.c         |   13 ++++++++++++-
 conf.h         |    1 +
 refclock.c     |    7 +++++--
 sys_generic.c  |   20 ++++++++++++--------
 5 files changed, 60 insertions(+), 22 deletions(-)


hooks/post-receive
--
chrony/chrony.git

-- 
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.