[chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 1.27-55-g52272f4 |
[ 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 52272f4dc5bc2dd7b8e057a308fbb0caa7181e1b (commit)
via 18a66a2ba8adb823816c924d44c401bacbbbf219 (commit)
from 8aa9eb19c826f3ea4a9c2ce5e3a71b74aeeb99d0 (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 52272f4dc5bc2dd7b8e057a308fbb0caa7181e1b
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date: Mon Jun 10 18:37:08 2013 +0200
Limit sources included in combining
Combine only sources whose distance is shorter than distance of the
selected source multiplied by the value of combinelimit and their
estimated frequencies are close to the frequency of the selected source.
Add outlyer status for sources which are selectable, but not included in
the combining. The status is displayed as '-' in the chronyc sources
output.
commit 18a66a2ba8adb823816c924d44c401bacbbbf219
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date: Wed Jun 29 18:45:31 2011 +0200
Resurrect source combining
This is based on the code that was removed in CVS revision 1.3 of
sources.c. The weighting is simplified and the code is moved to a new
function.
-----------------------------------------------------------------------
Summary of changes:
chrony.texi.in | 36 ++++++++++++++++++++--
client.c | 4 +-
cmdmon.c | 3 ++
conf.c | 23 ++++++++++++++
conf.h | 1 +
reports.h | 2 +-
sources.c | 89 ++++++++++++++++++++++++++++++++++++++++++++++++++++++--
7 files changed, 148 insertions(+), 10 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.