[chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 2.1.1-61-g67ce6bd

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-dev Archives ]


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  67ce6bd279b436b16dcb182ff3da631164ab829f (commit)
       via  770db1fe02b775f0ef1da8dad79ef26e7af01c2b (commit)
       via  d73394dde17e1a5bd7883b6b0f2bbb8a29c1aa4e (commit)
      from  eb0c7e33d2f89490236d8e8b79459f2eb8252a5b (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 67ce6bd279b436b16dcb182ff3da631164ab829f
Author: Bryan Christianson <bryan@xxxxxxxxxxxxx>
Date:   Fri Aug 28 23:21:01 2015 +1200

    sys_macosx: reset drift removal timer after spike in offset_sd
    
    When a large spike occurs in offset_sd the drift removal interval can be
    set to an excessively long time, although what ever event caused the
    perturbation has passed. At the next set_sync_status() we now compare
    the expected drift removal interval with that currently in effect. If
    they are significantly different, the current timer is cancelled and new
    cycle started using the new drift removal interval.

commit 770db1fe02b775f0ef1da8dad79ef26e7af01c2b
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Wed Aug 26 14:45:36 2015 +0200

    sys_linux: always call TMX_SetLeap() in set_leap()
    
    The optimization avoiding unnecessary setting of the kernel leap status
    can cause a problem when something outside chronyd sets the status to
    the new expected value. There will be no TMX_SetLeap() call which would
    update the saved status and the kernel status will be overwritten with
    the old (incorrect) value in a later TMX_*() call.
    
    Always call TMX_SetLeap() to save the new value and for the log message
    selection just check if a leap second has been applied.

commit d73394dde17e1a5bd7883b6b0f2bbb8a29c1aa4e
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Wed Aug 26 14:42:14 2015 +0200

    reference: call LCL_SetSystemLeap() only on leap changes

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

Summary of changes:
 reference.c     |    4 +++-
 sys_linux.c     |    8 +++-----
 sys_macosx.c    |   54 +++++++++++++++++++++++++++++++++---------------------
 wrap_adjtimex.c |    9 +--------
 wrap_adjtimex.h |    2 +-
 5 files changed, 41 insertions(+), 36 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.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/