Equivalent to V1.19.99.1

This is a verbatim copy of the files at that stage of the repository that was
built from the CVS import.  It allows future development to see a bit of recent
history, but without carrying around the baggage going back to 1997.  If that
is really required, git grafts can be used.

examples/chrony.keys.example

@@ -0,0 +1,27 @@
+#######################################################################
+# $Header: /cvs/src/chrony/examples/chrony.keys.example,v 1.1 2002/01/31 00:00:08 richard Exp $
+#
+# This is an example chrony keys file.  You should copy it to /etc/chrony.keys
+# after editing it to set up the key(s) you want to use.  In most situations,
+# you will require a single key (the 'commandkey') so that you can supply a
+# password to chronyc to enable you to modify chronyd's operation whilst it is
+# running.
+#
+# Copyright 2002 Richard P. Curnow
+#
+#######################################################################
+# A valid key line looks like this
+
+1 a_key
+
+# It must consist of an integer, followed by whitespace, followed by a block of
+# text with no spaces in it.  (You cannot put a space in a key).  If you wanted
+# to use the above line as your commandkey (i.e. chronyc password), you would
+# put the following line into chrony.conf (remove the # from the start):
+
+# commandkey 1
+
+# You might want to define more keys if you use the MD5 authentication facility
+# in the network time protocol to authenticate request/response packets between
+# trusted clients and servers.
+