CHRONYC(1) User's Manual CHRONYC(1)NAME
chronyc - command-line interface for chronyd
SYNOPSIS
chronyc [OPTIONS]
DESCRIPTION
chrony is a pair of programs for maintaining the accuracy of computer clocks.
chronyc is a command-line interface program which can be used to monitor chronyd's performance and to change various operating parameters
whilst it is running.
USAGE
A detailed description of all commands supported by chronyc is available via the documentation supplied with the distribution (chrony.txt
and chrony.texi).
OPTIONS
A summary of the options supported by chronyc is included below.
-h hostname
specify hostname
-p port-number
specify port-number
-n display raw IP addresses (don't attempt to look up hostnames)
-4 resolve hostnames only to IPv4 addresses
-6 resolve hostnames only to IPv6 addresses
-m allow multiple commands to be specified on the command line. Each argument will be interpreted as a whole command.
-f conf-file
This option can be used to specify an alternate location for the configuration file (default /etc/chrony.conf). The configuration
file is needed for the -a option.
-a With this option chronyc will try to authenticate automatically on start. It will read the configuration file, read the command key
from the keyfile and run the authhash and password commands.
command
specify command. If no command is given, chronyc will read commands interactively.
BUGS
To report bugs, please visit http://chrony.tuxfamily.org
SEE ALSO chronyd(8), chrony(1)
http://chrony.tuxfamily.org/
AUTHOR
Richard Curnow <rc@rc0.org.uk>
This man-page was written by Jan Schaumann <jschauma@netmeister.org> as part of "The Missing Man Pages Project". Please see
http://www.netmeister.org/misc/m2p2/index.html for details.
The complete chrony documentation is supplied in texinfo format.
chrony 1.29.1 January 2014 CHRONYC(1)
Check Out this Related Man Page
RNDC(8) BIND9 RNDC(8)NAME
rndc - name server control utility
SYNOPSIS
rndc [-b source-address] [-c config-file] [-k key-file] [-s server] [-p port] [-V] [-y key_id] {command}
DESCRIPTION
rndc controls the operation of a name server. It supersedes the ndc utility that was provided in old BIND releases. If rndc is invoked with
no command line options or arguments, it prints a short summary of the supported commands and the available options and their arguments.
rndc communicates with the name server over a TCP connection, sending commands authenticated with digital signatures. In the current
versions of rndc and named, the only supported authentication algorithm is HMAC-MD5, which uses a shared secret on each end of the
connection. This provides TSIG-style authentication for the command request and the name server's response. All commands sent over the
channel must be signed by a key_id known to the server.
rndc reads a configuration file to determine how to contact the name server and decide what algorithm and key it should use.
OPTIONS -b source-address
Use source-address as the source address for the connection to the server. Multiple instances are permitted to allow setting of both
the IPv4 and IPv6 source addresses.
-c config-file
Use config-file as the configuration file instead of the default, /etc/rndc.conf.
-k key-file
Use key-file as the key file instead of the default, /etc/rndc.key. The key in /etc/rndc.key will be used to authenticate commands sent
to the server if the config-file does not exist.
-s server
server is the name or address of the server which matches a server statement in the configuration file for rndc. If no server is
supplied on the command line, the host named by the default-server clause in the options statement of the rndc configuration file will
be used.
-p port
Send commands to TCP port port instead of BIND 9's default control channel port, 953.
-V
Enable verbose logging.
-y key_id
Use the key key_id from the configuration file. key_id must be known by named with the same algorithm and secret string in order for
control message validation to succeed. If no key_id is specified, rndc will first look for a key clause in the server statement of the
server being used, or if no server statement is present for that host, then the default-key clause of the options statement. Note that
the configuration file contains shared secrets which are used to send authenticated control commands to name servers. It should
therefore not have general read or write access.
For the complete set of commands supported by rndc, see the BIND 9 Administrator Reference Manual or run rndc without arguments to see its
help message.
LIMITATIONS
rndc does not yet support all the commands of the BIND 8 ndc utility.
There is currently no way to provide the shared secret for a key_id without using the configuration file.
Several error messages could be clearer.
SEE ALSO rndc.conf(5), rndc-confgen(8), named(8), named.conf(5), ndc(8), BIND 9 Administrator Reference Manual.
AUTHOR
Internet Systems Consortium
COPYRIGHT
Copyright (C) 2004, 2005, 2007 Internet Systems Consortium, Inc. ("ISC")
Copyright (C) 2000, 2001 Internet Software Consortium.
BIND9 June 30, 2000 RNDC(8)