File: README

package info (click to toggle)
chrony 1.14-7
  • links: PTS
  • area: main
  • in suites: woody
  • size: 1,480 kB
  • ctags: 2,091
  • sloc: ansic: 15,266; sh: 194; makefile: 113
file content (194 lines) | stat: -rw-r--r-- 6,762 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
This is the README for chrony.

What is chrony?
===============
Chrony is a pair of programs for maintaining the accuracy of computer
clocks.

chronyd is a (background) daemon program that can be started at boot
time.  This does most of the work.

chronyc is a command-line interface program which can be used to
monitor chronyd's performance and to change various operating
parateters whilst it is running.

chronyd's main function is to obtain measurements of the true (UTC)
time from one of several sources, and correct the system clock
accordingly.  It also works out the rate at which the system clock
gains or loses time and uses this information to keep it accurate
between measurements from the reference.

The reference time can be derived from either Network Time Protocol
(NTP) servers (preferred), or wristwatch-and-keyboard (via chronyc).
The main source of information about the Network Time Protocol is
http://www.eecis.udel.edu/~ntp.

It is designed so that it can work on computers which only have
intermittent access to reference sources, for example computers which
use a dial-up account to access the Internet.  Of course, it will work
on computers with permanent connections too.

In addition, the Linux 2.0.x (for x >= 32), 2.2.x and 2.3.x versions
can monitor the system's real time clock performance, so the system
can maintain accurate time even across reboots.

Typical accuracies available between 2 machines are

On an ethernet LAN : 100-200 microseconds, often much better
On a V32bis dial-up modem connection : 10's of milliseconds (from one
session to the next)

chronyd can also operate as an RFC1305-compatible NTP server and peer.


What will chrony run on?
========================

Chrony can be successfully built and run on

1. Linux v2.0.x, 2.1.x (partially), 2.2.x, 2.3.x (i386)

Linux 1.2.13 may work - the code has support but I haven't access to
anything to test it on. There is support for some patchlevels of Linux
2.1, but not the more recent ones - I haven't got access to a source
tree to check certain details.

2. Solaris 2.5/2.5.1 (Sparc 20 and Ultrasparc).

3. SunOS 4.1.4 (Sparc 2 and Sparc 20)

4. BSD/386 v1.1 has been reported to work using the SunOS 4.1 driver.

Any other system will require a porting exercise.  You would need to
start from one of the existing system-specific drivers and look into
the quirks of certain system calls and the kernel on your target
system.  (This is described in the manual).


How do I set it up?
===================

The file INSTALL gives instructions.  On supported systems the
compilation process should be automatic.

You will need an ANSI C compiler -- gcc is recommended.  Versions
2.7.2/2.7.2.2 are known to work.

The manual (in texinfo and text formats) describes how to set the
software up for the less straightforward cases.

What documentation is there?
============================

A manual is supplied in Texinfo format (chrony.texi) and
ready-formatted plain text (chrony.txt) in the distribution.

There is also information available on the chrony web pages, accessible
through the URL 

    http://go.to/chrony

What can chrony not do?
=======================

Compared to the `reference' RFC1305 implementation xntpd, chronyd does
not support hardware reference clocks, leap seconds or broadcast
modes.

Where are new versions announced?
=================================

There is a low volume mailing list hosted on egroups where new versions
and other important news relating to chrony is announced.  You can join
this list by sending mail to

chrony-announce-subscribe@egroups.com

These messages will be copied to chrony-users (see below).  I also try
to announce new versions on Freshmeat (http://freshmeat.net/).

I don't reliably announce via news any more - I don't tend to keep up
with news as I haven't enough time.

How can I get support for chrony?
and where can I discuss new features, possible bugs etc?
========================================================

There is a mailing list for chrony discussion (including questions and answers
of a support nature) hosted on Egroups.  To subscribe to this list, send mail
to

chrony-users-subscribe@egroups.com

The remit of this groups is
o Support question / answer forum
o Discussion about possible bugs, extensions, ports to other O/Ses etc
o Announcements of new releases (copies of messages to chrony-announce)
o Developer discussions for the time being - if sufficient traffic
  builds up, I'll start a separate list for this.

Note that due to family commitments (a 2 year-old and a 0 year-old), I
no longer have the time to give to supporting chrony that I once had.
Therefore, the mailing list should be your main route for support,
rather than mailing me directly.  Even if it's me that responds to your
question on the list, at least *ALL* subscribers then benefit from
seeing the discussion, rather than me taking up lots of time on
supporting people on a one-to-one basis.

But how can I contact the author if I need to?
==============================================

You can email me at <rpc@myself.com> (or equivalently through
chrony@go.to, or even through <chrony-users-owner@egroups.com>).  It
would be nice if:

- you include the word 'chrony' in the subject line (so my mail reader
can sort my mail by topic)

- you don't send complete log files, encoded binaries etc, without
editing such material down to just the relevant bits - a few tens of
lines at most.  (My dial-up connection handles large messages rather
slowly ...).

Acknowledgements
================

The following people have provided patches and other contributions to
the program :

Andrew Bishop <amb@gedanken.demon.co.uk>
    Fixes for bugs in logging when in daemon mode
    Fixes for compiler warnings
    Robustness improvements for drift file
    Improve installation (directory checking etc)
    Entries in contrib directory

Jim Knoble <jmknoble@pobox.com>
    Fixes for compiler warnings

Stephan I. Boettcher <stephan@nevis1.columbia.edu>
    Entries in contrib directory

Erik Bryer <ebryer@spots.ab.ca>
    Entries in contrib directory

Antti Jrvinen <costello@iki.fi>
    Advice on configuring for BSD/386

Ulrich Windl <ulrich.windl@rz.uni-regensburg.de> for the
    Providing me with information about the Linux 2.2 kernel
    functionality compared to 2.0.

Walter Haidinger <walter.haidinger@gmx.at>
    Providing me with login access to a Linux installation where v1.12
    wouldn't compile, so I could develop the fixes for v1.13.

Many other people have contributed bug reports and suggestions, sorry I
can't identify all of you by name.

Version control information
===========================

$Header: /cvs/src/chrony/README,v 1.14 2000/07/15 21:29:37 richard Exp $

vim:tw=72