[system-administrators-guide] Updated links to the Release Notes.
by jhradile
commit 3b16da35e1375f338ec35e1afdad95bb6ce568e5
Author: Jaromir Hradilek <jhradilek(a)redhat.com>
Date: Mon Jul 1 15:31:13 2013 +0200
Updated links to the Release Notes.
en-US/The_kdump_Crash_Recovery_Service.xml | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index 0e54203..4188ecb 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -46,7 +46,7 @@
<important>
<title>Make sure the system has enough memory</title>
<para>
- Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Rel..."><citetitle pubwork="section">Hardware Overview</citetitle></ulink> section of the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html"><citetitle pubwork="book">Fedora 17 Release Notes</citetitle></ulink>. When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/19/html/Release_Notes/sect-Rel..."><citetitle pubwork="section">Hardware Overview</citetitle></ulink> section of the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/19/html/Release_Notes/index.html"><citetitle pubwork="book">Fedora 19 Release Notes</citetitle></ulink>. When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
</para>
</important>
<section id="s3-kdump-configuration-firstboot-enable">
@@ -90,7 +90,7 @@
<important>
<title>Make sure the system has enough memory</title>
<para>
- Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Rel..."><citetitle pubwork="section">Hardware Overview</citetitle></ulink> section of the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html"><citetitle pubwork="book">Fedora 17 Release Notes</citetitle></ulink>. When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/19/html/Release_Notes/sect-Rel..."><citetitle pubwork="section">Hardware Overview</citetitle></ulink> section of the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/19/html/Release_Notes/index.html"><citetitle pubwork="book">Fedora 19 Release Notes</citetitle></ulink>. When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
</para>
</important>
<section id="s3-kdump-configuration-gui-enable">
@@ -385,7 +385,7 @@
<important>
<title>Make sure the system has enough memory</title>
<para>
- Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Rel..."><citetitle pubwork="section">Hardware Overview</citetitle></ulink> section of the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html"><citetitle pubwork="book">Fedora 17 Release Notes</citetitle></ulink>. When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/19/html/Release_Notes/sect-Rel..."><citetitle pubwork="section">Hardware Overview</citetitle></ulink> section of the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/19/html/Release_Notes/index.html"><citetitle pubwork="book">Fedora 19 Release Notes</citetitle></ulink>. When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
</para>
</important>
<important>
10 years, 10 months
[system-administrators-guide/18] Updated links to the Release Notes.
by jhradile
commit c397318fb84b834846b29b77d601778aa4286d66
Author: Jaromir Hradilek <jhradilek(a)redhat.com>
Date: Mon Jul 1 15:31:13 2013 +0200
Updated links to the Release Notes.
en-US/The_kdump_Crash_Recovery_Service.xml | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index 0e54203..f4c1ce3 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -46,7 +46,7 @@
<important>
<title>Make sure the system has enough memory</title>
<para>
- Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Rel..."><citetitle pubwork="section">Hardware Overview</citetitle></ulink> section of the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html"><citetitle pubwork="book">Fedora 17 Release Notes</citetitle></ulink>. When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/18/html/Release_Notes/sect-Rel..."><citetitle pubwork="section">Hardware Overview</citetitle></ulink> section of the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/18/html/Release_Notes/index.html"><citetitle pubwork="book">Fedora 18 Release Notes</citetitle></ulink>. When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
</para>
</important>
<section id="s3-kdump-configuration-firstboot-enable">
@@ -90,7 +90,7 @@
<important>
<title>Make sure the system has enough memory</title>
<para>
- Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Rel..."><citetitle pubwork="section">Hardware Overview</citetitle></ulink> section of the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html"><citetitle pubwork="book">Fedora 17 Release Notes</citetitle></ulink>. When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/18/html/Release_Notes/sect-Rel..."><citetitle pubwork="section">Hardware Overview</citetitle></ulink> section of the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/18/html/Release_Notes/index.html"><citetitle pubwork="book">Fedora 18 Release Notes</citetitle></ulink>. When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
</para>
</important>
<section id="s3-kdump-configuration-gui-enable">
@@ -385,7 +385,7 @@
<important>
<title>Make sure the system has enough memory</title>
<para>
- Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Rel..."><citetitle pubwork="section">Hardware Overview</citetitle></ulink> section of the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/index.html"><citetitle pubwork="book">Fedora 17 Release Notes</citetitle></ulink>. When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/18/html/Release_Notes/sect-Rel..."><citetitle pubwork="section">Hardware Overview</citetitle></ulink> section of the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/18/html/Release_Notes/index.html"><citetitle pubwork="book">Fedora 18 Release Notes</citetitle></ulink>. When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by the user, and defaults to 128 MB plus 64 MB for each TB of physical memory (that is, a total of 192 MB for a system with 1 TB of physical memory).
</para>
</important>
<important>
10 years, 10 months
[system-administrators-guide] Removed empty paragraphs.
by jhradile
commit d966daeba995449fde4d800e823ee0b4ea12b5ce
Author: Jaromir Hradilek <jhradilek(a)redhat.com>
Date: Mon Jul 1 15:19:21 2013 +0200
Removed empty paragraphs.
en-US/Configuring_NTP_using_the_Chrony_suite.xml | 14 --------------
1 files changed, 0 insertions(+), 14 deletions(-)
---
diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
index 10c97d9..1d0a90a 100644
--- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml
+++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
@@ -113,9 +113,6 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas
</section>
<section id="sect-Understanding_chrony_and-its_configuration">
<title>Understanding chrony and Its Configuration</title>
- <para>
-
- </para>
<section id="sect-Understanding_chronyd">
<title>Understanding chronyd</title>
<para>
@@ -495,9 +492,6 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command
<section id="sect-Using_chrony">
<title>Using chrony</title>
- <para>
-
- </para>
<section id="sect-Checking_if_chrony_is_installed">
@@ -539,8 +533,6 @@ chronyd.service - NTP client/server
To ensure <systemitem class="daemon">chronyd</systemitem> starts automatically at system start, issue the following command as root:
<screen>~]# <command>systemctl enable chronyd</command></screen>
</para>
- <para>
- </para>
</section>
<section id="sect-Stopping_chronyd">
<title>Stopping chronyd</title>
@@ -873,9 +865,6 @@ This is the estimated error bounds on Freq (again in parts per million).
<section id="sect-Setting_up_chrony_for_different_environments">
<title>Setting Up chrony for Different Environments</title>
- <para>
-
- </para>
<section id="sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">
@@ -974,9 +963,6 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t
<section id="sect-Using_chronyc">
<title>Using chronyc</title>
- <para>
-
- </para>
<section id="sect-Using_chronyc_chronyc_to_control_cronyd">
10 years, 10 months
[system-administrators-guide/18] Removed empty paragraphs.
by jhradile
commit a00b1f453099086b4cfb0a52e0f5dd1d1b70e336
Author: Jaromir Hradilek <jhradilek(a)redhat.com>
Date: Mon Jul 1 15:19:21 2013 +0200
Removed empty paragraphs.
en-US/Configuring_NTP_using_the_Chrony_suite.xml | 14 --------------
1 files changed, 0 insertions(+), 14 deletions(-)
---
diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
index f3d1103..d783f53 100644
--- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml
+++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
@@ -113,9 +113,6 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas
</section>
<section id="sect-Understanding_chrony_and-its_configuration">
<title>Understanding chrony and Its Configuration</title>
- <para>
-
- </para>
<section id="sect-Understanding_chronyd">
<title>Understanding chronyd</title>
<para>
@@ -495,9 +492,6 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command
<section id="sect-Using_chrony">
<title>Using chrony</title>
- <para>
-
- </para>
<section id="sect-Checking_if_chrony_is_installed">
@@ -539,8 +533,6 @@ chronyd.service - NTP client/server
To ensure <systemitem class="daemon">chronyd</systemitem> starts automatically at system start, issue the following command as root:
<screen>~]# <command>systemctl enable chronyd</command></screen>
</para>
- <para>
- </para>
</section>
<section id="sect-Stopping_chronyd">
<title>Stopping chronyd</title>
@@ -873,9 +865,6 @@ This is the estimated error bounds on Freq (again in parts per million).
<section id="sect-Setting_up_chrony_for_different_environments">
<title>Setting Up chrony for Different Environments</title>
- <para>
-
- </para>
<section id="sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">
@@ -974,9 +963,6 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t
<section id="sect-Using_chronyc">
<title>Using chronyc</title>
- <para>
-
- </para>
<section id="sect-Using_chronyc_chronyc_to_control_cronyd">
10 years, 10 months
[system-administrators-guide/18] Added the NetworkManager chapter to the preface.
by jhradile
commit a777a21d498893d81044f6c516c1b4a6640fff38
Author: Jaromir Hradilek <jhradilek(a)redhat.com>
Date: Mon Jul 1 14:50:50 2013 +0200
Added the NetworkManager chapter to the preface.
en-US/Preface.xml | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
---
diff --git a/en-US/Preface.xml b/en-US/Preface.xml
index b8fa126..916928c 100644
--- a/en-US/Preface.xml
+++ b/en-US/Preface.xml
@@ -88,11 +88,9 @@
<para>
This part describes how to configure the network on &MAJOROS;.
</para>
- <!-- jhradilek: TBD F15: Uncomment this as soon as the NetworkManager chapter is updated.
<para>
<xref linkend="ch-NetworkManager" /> focuses on <application>NetworkManager</application>, a dynamic network control and configuration system that attempts to keep network devices and connections up and active when they are available. Read this chapter for information how to run the <systemitem class="service">NetworkManager</systemitem> daemon, and how to interact with it using the corresponding applet for the notification area.
</para>
- -->
<para>
<xref linkend="ch-Network_Interfaces" /> explores various interface configuration files, interface control scripts, and network function files located in the <filename class="directory">/etc/sysconfig/network-scripts/</filename> directory. Read this chapter for information how to use these files to configure network interfaces.
</para>
10 years, 10 months
[system-administrators-guide/18] Ensured that the formatting of commands is consistent.
by jhradile
commit a7fb462e1102631d1fbf3bdb98121159794d91cd
Author: Jaromir Hradilek <jhradilek(a)redhat.com>
Date: Mon Jul 1 14:47:04 2013 +0200
Ensured that the formatting of commands is consistent.
en-US/Configuring_NTP_using_the_Chrony_suite.xml | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
index a412a0a..f3d1103 100644
--- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml
+++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
@@ -504,7 +504,7 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command
<title>Checking if chrony is Installed</title>
<para>
To check if <application>chrony</application> is installed, run the following command as root:
- <screen>~]# yum install chrony</screen>
+ <screen>~]# <command>yum install chrony</command></screen>
The default location for the <application>chrony</application> daemon is <filename>/usr/local/sbin/chronyd</filename>.
</para>
</section>
@@ -513,7 +513,7 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command
<title>Installing chrony</title>
<para>
To install <application>chrony</application>, run the following command as root:
- <screen>~]# yum install chrony -y</screen>
+ <screen>~]# <command>yum install chrony -y</command></screen>
The default installation directory is <filename>/usr/local/sbin/</filename>
</para>
</section>
@@ -983,7 +983,7 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t
<title>Using chronyc to Control cronyd</title>
<para>
To make changes using the command line utility <application>chronyc</application> in interactive mode, enter the following command as root:
- <screen>~]# chronyc</screen>
+ <screen>~]# <command>chronyc</command></screen>
<application>chronyc</application> must run as root if some of the restricted commands are to be used.
</para>
<para>
10 years, 10 months
[system-administrators-guide/18] Corrected all titles to follow the same rules.
by jhradile
commit 2e583feb1f3436784372a6828ed202adcace6df1
Author: Jaromir Hradilek <jhradilek(a)redhat.com>
Date: Mon Jul 1 14:41:51 2013 +0200
Corrected all titles to follow the same rules.
en-US/Configuring_NTP_using_the_Chrony_suite.xml | 32 +++++++++++-----------
1 files changed, 16 insertions(+), 16 deletions(-)
---
diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
index c4b6a72..a412a0a 100644
--- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml
+++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
@@ -6,7 +6,7 @@
<!--Topics, Concepts:-->
<chapter id="chap-Configuring_NTP_Using_the_chrony_Suite">
- <title>Configuring NTP Using The chrony Suite</title>
+ <title>Configuring NTP Using the chrony Suite</title>
<para>
Accurate time keeping is important for a number of reasons in IT. In networking for example, accurate time stamps in packets and logs are required. In Linux systems, the <systemitem class="protocol">NTP</systemitem> protocol is implemented by a daemon running in user space.</para>
<para>
@@ -16,13 +16,13 @@
There is a choice between the daemons <systemitem class="daemon">ntpd</systemitem> and <systemitem class="daemon">chronyd</systemitem>, which are available from the repos in the <package>ntp</package> and <package>chrony</package> packages respectively. This section describes the use of the <application>chrony</application> suite of utilities to update the daemon on systems that do not fit into the conventional permanently networked, always on, dedicated server category.
</para>
<section id="sect-Introduction_to_the_chrony_suite">
- <title>Introduction To The chrony Suite</title>
+ <title>Introduction to the chrony Suite</title>
<para>
<application>Chrony</application> consists of <systemitem class="daemon">chronyd</systemitem>, a daemon that runs in user space, and <application>chronyc</application>, a command line program for making adjustments to <systemitem class="daemon">chronyd</systemitem>. Systems which are not permanently connected, or not permanently powered up, take a relatively long time to adjust their system clocks using the <systemitem class="protocol">NTP</systemitem> time protocol. This is because many small corrections are made based on observations of the clocks drift and offset. Temperature changes, which may be significant when powering up a system, affect the stability of hardware clocks. Although adjustments begin within a few milliseconds of booting a system, acceptable accuracy may take anything from ten seconds from a warm restart to a number of hours depending on your requirements, operating environment and hardware. <application>chrony</application> is a different implementat
ion of the <systemitem class="protocol">NTP</systemitem> protocol than <systemitem class="daemon">ntpd</systemitem>, it can adjust the system clock more rapidly.
</para>
<section id="sect-differences_between_ntpd_and_chronyd">
- <title>Differences Between ntpd And chronyd</title>
+ <title>Differences Between ntpd and chronyd</title>
<para>
One of the main differences between <systemitem class="daemon">ntpd</systemitem> and <systemitem class="daemon">chronyd</systemitem> is in the
algorithms used to control the computer's clock. Things <systemitem class="daemon">chronyd</systemitem> can do better than <systemitem class="daemon">ntpd</systemitem> are:
@@ -112,7 +112,7 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas
</section>
</section>
<section id="sect-Understanding_chrony_and-its_configuration">
- <title>Understanding chrony And Its Configuration</title>
+ <title>Understanding chrony and Its Configuration</title>
<para>
</para>
@@ -130,7 +130,7 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas
</section>
<section id="sect-Understanding_the_chrony_configuration_commands">
- <title>Understanding The chrony Configuration Commands</title>
+ <title>Understanding the chrony Configuration Commands</title>
<para>
<systemitem class="daemon">chronyd</systemitem>'s default config file is <filename>/etc/chrony.conf</filename>. The <option>-f</option> option can be used to specify an alternate config file path. Refer to the <systemitem class="daemon">chronyd</systemitem> man page for further options. We present here a selection of configuration options. For a complete list of the directives that can be used see <citetitle pubwork="webpage">http://chrony.tuxfamily.org/manual.html#Configuration-file</citetitle>
<variablelist>
@@ -409,7 +409,7 @@ Not all real-time clocks are supported as their code system-specific.
</section>
<section id="sect-Security_with_chronyc">
- <title>Security With chronyc</title>
+ <title>Security with chronyc</title>
<para>
As access to <application>chronyc</application> allows changing <systemitem class="daemon">chronyd</systemitem> just as editing the configuration files would, access to <application>chronyc</application> should be limited. Passwords or their hashes can be specified in the key file, to restrict the use of <application>chronyc</application>. One of the entries is used to restrict the use of operational commands and is referred to as the command key. In the default configuration, a random command key is generated automatically on start. It should not be necessary to specify or alter it manually.</para>
<para>Other entries in the key file can be used as <systemitem class="protocol">NTP</systemitem> keys to authenticate packets received from remote <systemitem class="protocol">NTP</systemitem> servers or peers. The two sides need to share a key with identical ID, hash type and password in their key file. This requires manually creating the keys and copying them over a secure medium, such as <systemitem class="protocol">SSH</systemitem>. If the key ID was, for example, 10 then the systems that act as clients must have a line in their configuration files in the following format:
@@ -501,7 +501,7 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command
<section id="sect-Checking_if_chrony_is_installed">
- <title>Checking If chrony Is Installed</title>
+ <title>Checking if chrony is Installed</title>
<para>
To check if <application>chrony</application> is installed, run the following command as root:
<screen>~]# yum install chrony</screen>
@@ -520,7 +520,7 @@ To install <application>chrony</application>, run the following command as root:
<section id="sect-Checking_the_Status_of_chronyd">
- <title>Checking The Status Of chronyd</title>
+ <title>Checking the Status of chronyd</title>
<para>
To check the status of <systemitem class="daemon">chronyd</systemitem>, issue the following command:
<screen>~]$ <command>systemctl status chronyd</command>
@@ -556,7 +556,7 @@ chronyd.service - NTP client/server
<section id="sect-Checking_if_chrony_is_synchronized">
- <title>Checking If chrony Is Synchronized</title>
+ <title>Checking if chrony is Synchronized</title>
<para>
To check if <application>chrony</application> is synchronized, make use of the <command>tracking</command>, <command>sources</command>, and <command>sourcestats</command> commands.
</para>
@@ -855,7 +855,7 @@ This is the estimated error bounds on Freq (again in parts per million).
</section>
<section id="sect-Adjusting-the-System_Clock">
- <title>Manualy Adjusting The System Clock</title>
+ <title>Manualy Adjusting the System Clock</title>
<para>
To update, or step, the system clock immediately, bypassing any adjustments in progress by slewing the clock, issue the following commands as root:
<screen>~]# <command>chronyc</command>
@@ -872,14 +872,14 @@ This is the estimated error bounds on Freq (again in parts per million).
</section>
<section id="sect-Setting_up_chrony_for_different_environments">
- <title>Setting up chrony For Different Environments</title>
+ <title>Setting Up chrony for Different Environments</title>
<para>
</para>
<section id="sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">
- <title>Setting Up chrony For A System Which Is Infrequently Connected</title>
+ <title>Setting Up chrony for a System Which is Infrequently Connected</title>
<para>
This example is intended for systems which use dial-on-demand connections. The normal configuration should be sufficient for mobile and virtual devices which connect intermittently. First, review and confirm that the default settings in the <filename>/etc/chrony.conf</filename> are similar to the following:
<screen>driftfile /var/lib/chrony/drift
@@ -907,7 +907,7 @@ The <option>offline</option> option can be useful in preventing systems from try
</para>
<section id="sect-Configuring_chrony_to_connect_and_disconnect">
- <title>Configuring chrony To Connect And Disconnect</title>
+ <title>Configuring chrony to Connect and Disconnect</title>
<para>
Using your editor running as root, add the following to the <filename>/etc/ppp/ip-up</filename> file:
<screen>
@@ -935,7 +935,7 @@ offline
<section id="sect-Setting_up_chrony_for_a_system_in_an_isolated_network">
- <title>Setting Up chrony For A System In An Isolated Network</title>
+ <title>Setting Up chrony for a System in an Isolated Network</title>
<para>
For a network that is never connected to the Internet, one computer is selected to be the master timeserver. The other computers are either direct clients of the master, or clients of clients. On the master, the drift file must be manually set with the average rate of drift of the system clock. If the master is rebooted it will obtain the time from surrounding systems and take an average to set its system clock. Thereafter it resumes applying adjustments based on the drift file. The drift file will be updated automatically when the <command>settime</command> command is used.
</para>
@@ -980,7 +980,7 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t
<section id="sect-Using_chronyc_chronyc_to_control_cronyd">
- <title>Using chronyc To Control cronyd</title>
+ <title>Using chronyc to Control cronyd</title>
<para>
To make changes using the command line utility <application>chronyc</application> in interactive mode, enter the following command as root:
<screen>~]# chronyc</screen>
@@ -1000,7 +1000,7 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t
</section>
<section id="sect-Using_chronyc_for_remote_administration">
-<title>Using chronyc For Remote Administration</title>
+<title>Using chronyc for Remote Administration</title>
<para>
To configure <application>chrony</application> to connect to a remote instance of <systemitem class="daemon">chronyd</systemitem>, issue a command as root in the following format:
<screen>~]# <command>chronyc <option>-h</option> <replaceable>hostname</replaceable></command></screen>
10 years, 10 months
[system-administrators-guide/18] Updated the description of the Basic System Configuration part.
by jhradile
commit 8456f6769d3e1704e27efc4c6d01c4b4fa167b14
Author: Jaromir Hradilek <jhradilek(a)redhat.com>
Date: Mon Jul 1 14:32:37 2013 +0200
Updated the description of the Basic System Configuration part.
en-US/System_Administrators_Guide.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/System_Administrators_Guide.xml b/en-US/System_Administrators_Guide.xml
index edef757..ecf5a1f 100644
--- a/en-US/System_Administrators_Guide.xml
+++ b/en-US/System_Administrators_Guide.xml
@@ -11,7 +11,7 @@
<title>Basic System Configuration</title>
<partintro>
<para>
- This part covers basic system administration tasks such as keyboard configuration, date and time configuration, and managing users and groups.
+ This part covers basic system administration tasks such as keyboard configuration, date and time configuration, installation and initial setup of an NTP server, and managing users and groups.
</para>
</partintro>
<xi:include href="Configuring_the_Language_and_Keyboard.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
10 years, 10 months
[system-administrators-guide/18] Added the Chrony chapter to the Preface.
by jhradile
commit 6ba24fa9c4d94d94f1ef330303348098c4c6f96b
Author: Jaromir Hradilek <jhradilek(a)redhat.com>
Date: Mon Jul 1 14:28:22 2013 +0200
Added the Chrony chapter to the Preface.
en-US/Configuring_NTP_using_the_Chrony_suite.xml | 2 +-
en-US/Preface.xml | 7 +++++--
2 files changed, 6 insertions(+), 3 deletions(-)
---
diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
index 57c11c0..c4b6a72 100644
--- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml
+++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
@@ -5,7 +5,7 @@
]>
<!--Topics, Concepts:-->
-<chapter id="chap-Networking_Guide-Configuring_NTP_using_the_chrony_suite">
+<chapter id="chap-Configuring_NTP_Using_the_chrony_Suite">
<title>Configuring NTP Using The chrony Suite</title>
<para>
Accurate time keeping is important for a number of reasons in IT. In networking for example, accurate time stamps in packets and logs are required. In Linux systems, the <systemitem class="protocol">NTP</systemitem> protocol is implemented by a daemon running in user space.</para>
diff --git a/en-US/Preface.xml b/en-US/Preface.xml
index d606a61..b8fa126 100644
--- a/en-US/Preface.xml
+++ b/en-US/Preface.xml
@@ -52,13 +52,16 @@
<term><xref linkend="part-Basic_System_Configuration" /></term>
<listitem>
<para>
- This part covers basic system administration tasks such as keyboard configuration, date and time configuration, and managing users and groups.
+ This part covers basic system administration tasks such as keyboard configuration, date and time configuration, installation and initial setup of an NTP server, and managing users and groups.
</para>
<para>
<xref linkend="ch-Configuring_the_Language_and_Keyboard" /> covers basic language and keyboard setup. Read this chapter if you need to configure the language of your desktop, change the keyboard layout, or add the keyboard layout indicator to the panel.
</para>
<para>
- <xref linkend="ch-Configuring_the_Date_and_Time" /> covers the configuration of the system date and time. Read this chapter if you need to change the date and time setup, or configure the system to synchronize the clock with a remote Network Time Protocol (NTP) server.
+ <xref linkend="ch-Configuring_the_Date_and_Time" /> covers the configuration of the system date and time. Read this chapter if you need to set or change the date and time.
+ </para>
+ <para>
+ <xref linkend="chap-Configuring_NTP_Using_the_chrony_Suite" /> covers the installation and configuration of the chrony suite, a client and a server for the Network Time Protocol (NTP). Read this chapter if you need to configure the system to synchronize the clock with a remote NTP server, or set up an NTP server on this system.
</para>
<para>
<xref linkend="ch-Managing_Users_and_Groups" /> covers the management of users and groups in a graphical user interface and on the command line. Read this chapter if you need to manage users and groups on your system, or enable password aging.
10 years, 10 months
[system-administrators-guide/18] Grouping sections as structure was too "flat"
by jhradile
commit 6edc62aa0ec67c2e5df3e5516eb32d3b1c8ca88e
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Sat Jun 29 18:47:40 2013 +0200
Grouping sections as structure was too "flat"
en-US/Configuring_NTP_using_the_Chrony_suite.xml | 34 ++++++++++++++++++++-
1 files changed, 32 insertions(+), 2 deletions(-)
---
diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
index a7914a3..57c11c0 100644
--- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml
+++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
@@ -20,7 +20,6 @@ There is a choice between the daemons <systemitem class="daemon">ntpd</systemite
<para>
<application>Chrony</application> consists of <systemitem class="daemon">chronyd</systemitem>, a daemon that runs in user space, and <application>chronyc</application>, a command line program for making adjustments to <systemitem class="daemon">chronyd</systemitem>. Systems which are not permanently connected, or not permanently powered up, take a relatively long time to adjust their system clocks using the <systemitem class="protocol">NTP</systemitem> time protocol. This is because many small corrections are made based on observations of the clocks drift and offset. Temperature changes, which may be significant when powering up a system, affect the stability of hardware clocks. Although adjustments begin within a few milliseconds of booting a system, acceptable accuracy may take anything from ten seconds from a warm restart to a number of hours depending on your requirements, operating environment and hardware. <application>chrony</application> is a different implementat
ion of the <systemitem class="protocol">NTP</systemitem> protocol than <systemitem class="daemon">ntpd</systemitem>, it can adjust the system clock more rapidly.
</para>
- </section>
<section id="sect-differences_between_ntpd_and_chronyd">
<title>Differences Between ntpd And chronyd</title>
@@ -111,7 +110,13 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas
</listitem>
</itemizedlist>
</section>
-<section id="sect-Understanding_chronyd">
+ </section>
+ <section id="sect-Understanding_chrony_and-its_configuration">
+ <title>Understanding chrony And Its Configuration</title>
+ <para>
+
+ </para>
+ <section id="sect-Understanding_chronyd">
<title>Understanding chronyd</title>
<para>
The <application>chrony</application> daemon, <systemitem class="daemon">chronyd</systemitem>, running in user space, makes adjustments to the system clock which is running in the kernel. It does this by consulting external time sources, using the <systemitem class="protocol">NTP</systemitem> protocol, when ever network access allows it to do so. When external references are not available, <systemitem class="daemon">chronyd</systemitem> will use the last calculated drift stored in the drift file. It can also be commanded manually to make corrections, by <application>chronyc</application>.
@@ -484,9 +489,17 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command
</simplelist>.
</para>
</section>
+</section>
<!--Topics, Tasks:-->
+ <section id="sect-Using_chrony">
+ <title>Using chrony</title>
+ <para>
+
+ </para>
+
+
<section id="sect-Checking_if_chrony_is_installed">
<title>Checking If chrony Is Installed</title>
<para>
@@ -856,6 +869,14 @@ This is the estimated error bounds on Freq (again in parts per million).
In &MAJOROS;, the real-time clock should not be manually adjusted as this would interfere with <application>chrony</application>'s need to measure the rate at which the real-time clock drifts if it was adjusted at random intervals. By default, <application>rtcsync</application> will inform the kernel the system clock is synchronized and the kernel will update the real-time clock in 11 minute intervals.
</para>
</section>
+</section>
+
+<section id="sect-Setting_up_chrony_for_different_environments">
+ <title>Setting up chrony For Different Environments</title>
+ <para>
+
+ </para>
+
<section id="sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">
<title>Setting Up chrony For A System Which Is Infrequently Connected</title>
@@ -949,6 +970,14 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t
</para>
</section>
+</section>
+
+<section id="sect-Using_chronyc">
+ <title>Using chronyc</title>
+ <para>
+
+ </para>
+
<section id="sect-Using_chronyc_chronyc_to_control_cronyd">
<title>Using chronyc To Control cronyd</title>
@@ -999,6 +1028,7 @@ Note that commands issued at the <application>chrony</application> command promp
</para>
</section>
+</section>
<!--Topics, Reference-->
<section id="sect-additional_resources">
10 years, 10 months