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

The branch, master has been updated
       via  8f7ab95ff09e8d3a3f0aa56fb902ab20c6de0ae8 (commit)
       via  042c67074749268cf4aadad6efc552c7c641d461 (commit)
       via  cacbe9976fb613204199a98664082cb5204a6807 (commit)
       via  8efec1d6406f901f0494e641fa63bda51378f672 (commit)
       via  c44d282f0b1f37cc0eb5a06e3039594b4d48aeb6 (commit)
       via  4432f29bd2dacdd1e8e6dead420418a67ffd68e5 (commit)
       via  5fee3ed5e98604404d8d6d906f249a92251f2f5b (commit)
       via  b76ea642633b7a7bd9448fad2916b757fe050338 (commit)
       via  ed904f08a4b2221386d2b4ae79baab6185441d16 (commit)
       via  96cc80ffc87701dc0eaeccf2cf5e387436b13d5b (commit)
       via  ab99373cfcd01be5541c39213c6d58294dc46bac (commit)
       via  dbfb49384bd803409e8d43b98198211eb604de6f (commit)
       via  14bb9f29a3c2af359f8726ad00e2fa9e20394fc8 (commit)
      from  16519ee2cc5eaed53c946b2a9cf3c56ad7df6be1 (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 8f7ab95ff09e8d3a3f0aa56fb902ab20c6de0ae8
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Fri Jan 6 11:52:20 2017 +0100

    doc: update NEWS

commit 042c67074749268cf4aadad6efc552c7c641d461
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Fri Jan 6 11:06:42 2017 +0100

    doc: improve chrony.conf man page

commit cacbe9976fb613204199a98664082cb5204a6807
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Thu Jan 5 16:37:28 2017 +0100

    ntp: add options for compensating HW timestamping errors

commit 8efec1d6406f901f0494e641fa63bda51378f672
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Thu Jan 5 16:27:27 2017 +0100

    ntp: add sanity check for HW timestamps
    
    Accept HW timestamp only if it doesn't differ from the kernel/daemon
    timestamp by more than one second.

commit c44d282f0b1f37cc0eb5a06e3039594b4d48aeb6
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Thu Jan 5 15:37:34 2017 +0100

    ntp: ignore zero HW timestamps
    
    Apparently, zero HW timestamps are possible with buggy drivers/HW.

commit 4432f29bd2dacdd1e8e6dead420418a67ffd68e5
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Thu Jan 5 12:03:36 2017 +0100

    sources: try to replace jittery sources
    
    Similarly to falsetickers, distant, and unreachable sources, try to
    replace sources that have jitter larger than maxjitter.

commit 5fee3ed5e98604404d8d6d906f249a92251f2f5b
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Thu Jan 5 11:48:34 2017 +0100

    client: print refid also as string in ntpdata output

commit b76ea642633b7a7bd9448fad2916b757fe050338
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Thu Jan 5 11:29:55 2017 +0100

    ntp: log warning when KoD RATE is received in non-burst mode

commit ed904f08a4b2221386d2b4ae79baab6185441d16
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Wed Jan 4 15:46:41 2017 +0100

    hwclock: return timestamp error
    
    For now, when converting a raw timestamp, return error of the last
    sample as the maximum error of the timestamp. This is needed to include
    the PHC reading delay in the NTP dispersion.

commit 96cc80ffc87701dc0eaeccf2cf5e387436b13d5b
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Wed Jan 4 15:40:52 2017 +0100

    ntp: improve dispersion calculation
    
    Instead of adding precision (sum of the local and remote precision) to
    the TX and RX timestamp error, include only the maximum.

commit ab99373cfcd01be5541c39213c6d58294dc46bac
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Tue Jan 3 12:05:43 2017 +0100

    conf: change default rate limiting parameters
    
    Change the default NTP rate limiting leak to 2 (25%). Change the default
    command rate limiting interval to -4 (16 packets per second) and burst
    to 8, so the interval is the only difference between NTP and command
    rate limiting defaults.

commit dbfb49384bd803409e8d43b98198211eb604de6f
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Tue Jan 3 11:34:34 2017 +0100

    clientlog: disable NTP response rate limiting by default
    
    This reverts commit 50022e928644e3d727eaf8a7a8b334f3c998223c.
    
    Testing showed that ntpd as an NTP client performs poorly when it's
    getting only 25% of responses. At least for now, disable rate limiting
    by default again.

commit 14bb9f29a3c2af359f8726ad00e2fa9e20394fc8
Author: Miroslav Lichvar <mlich...@redhat.com>
Date:   Tue Jan 3 11:22:53 2017 +0100

    ntp: calculate delay relative to local frequency
    
    This should be more accurate as local frequency is usually
    combined from multiple sources. This is a partial revert of commit
    23a4e8b38d873ce1246c4ef43a05d92c442a9f26.

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

Summary of changes:
 NEWS                 |   3 +-
 client.c             |   7 +++-
 clientlog.c          |  34 +++++++++++------
 conf.c               |  94 +++++++++++++++++++++++++++++++++++++----------
 conf.h               |   7 ++--
 doc/chrony.conf.adoc | 101 +++++++++++++++++++++++++++++++--------------------
 doc/chronyc.adoc     |   2 +-
 hwclock.c            |   8 +++-
 ntp_core.c           |  16 ++++----
 ntp_io.c             |   8 +++-
 ntp_io_linux.c       |  71 +++++++++++++++++++++++-------------
 sources.c            |   5 ++-
 12 files changed, 236 insertions(+), 120 deletions(-)


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

-- 
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" 
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the 
subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

Reply via email to