[chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 1.26-41-g824e86a

[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  824e86a82fb8aa5058513b4c89ae2e1c7d6e348d (commit)
       via  2a5c045c3dc2a8a1a69854e793c155a07ffaca7d (commit)
      from  f7c65a4b8858b0e6a228c27d78bf746ae064fa17 (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 824e86a82fb8aa5058513b4c89ae2e1c7d6e348d
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Fri Feb 24 10:54:37 2012 +0100

    Add leap status to tracking log and report

commit 2a5c045c3dc2a8a1a69854e793c155a07ffaca7d
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Thu Feb 23 18:48:24 2012 +0100

    Add support for reading leap second data from tz database
    
    leapsectz directive is used to set the name of the timezone in the
    system tz database which chronyd can use to find out when will the next
    leap second occur.  It will periodically check if dates Jun 30 23:59:60
    and Dec 31 23:59:60 are valid in that timezone. This is mainly useful
    with reference clocks which don't provide the leap second information.
    It is not necessary to restart chronyd if the tz database is updated
    with a new leap second at least 12 hours before the event.

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

Summary of changes:
 candm.h     |    3 +-
 chrony.texi |   42 ++++++++++++++++++++----
 client.c    |   22 ++++++++++++-
 cmdmon.c    |    3 +-
 conf.c      |   23 +++++++++++++
 conf.h      |    1 +
 reference.c |  103 +++++++++++++++++++++++++++++++++++++++++++++++++++--------
 reports.h   |    1 +
 8 files changed, 174 insertions(+), 24 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.