[system-administrators-guide] Removing the ntpdate section. Deprecated.

[stephenw]

commit 3361c423be92efa2a77c037ab0416ee56e4a49bf
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Wed Oct 30 20:43:59 2013 +0100

    Removing the ntpdate section. Deprecated.

 en-US/Configuring_NTP_Using_ntpd.xml |   28 ----------------------------
 1 files changed, 0 insertions(+), 28 deletions(-)
---
diff --git a/en-US/Configuring_NTP_Using_ntpd.xml b/en-US/Configuring_NTP_Using_ntpd.xml
index cfd651b..287837c 100644
--- a/en-US/Configuring_NTP_Using_ntpd.xml
+++ b/en-US/Configuring_NTP_Using_ntpd.xml
@@ -394,34 +394,6 @@ synchronised to NTP server (10.5.26.10) at stratum 2
 
   </section>
 
-<section id="s1-Configure_ntpdate_servers">
-  <title>Configure ntpdate Servers</title>
-  <para>
-    The purpose of the <systemitem class="daemon">ntpdate</systemitem> service is to set the clock during system boot. This can be used to ensure that the services started after <systemitem class="daemon">ntpdate</systemitem> will have the  correct time and will not observe a jump in the clock. The use of <systemitem class="daemon">ntpdate</systemitem> and the list of step-tickers is considered deprecated and so <application>Red Hat Enterprise Linux 6</application> uses the <option>-g</option> option to the <command>ntpd</command> command by default and not <systemitem class="daemon">ntpdate</systemitem>. However, the <option>-g</option> option only enables <systemitem class="daemon">ntpd</systemitem> to ignore the offset limit of 1000s and attempt to synchronize the time. It does not guarantee the time will be correct when other programs or services are started. Therefore the <systemitem class="daemon">ntpdate</systemitem> service can be useful when <systemitem class="daemo
 n">ntpd</systemitem> is disabled or if there are services which need to be started with the correct time and not observe a jump in the clock.
-  </para>
- <para>
-  To check if the <systemitem class="daemon">ntpdate</systemitem> service is enabled to run at system start, issue the following command:
-  <screen>~]$ <command>chkconfig --list ntpdate</command>
-ntpdate        	0:off	1:off	2:on	3:on	4:on	5:on	6:off</screen>
-</para>
-<para>
- To enable the service to run at system start, issue the following command as <systemitem class="username">root</systemitem>:
-  <screen>~]# <command>chkconfig ntpdate on</command></screen>
-</para>
-
-<para>
-  To configure <systemitem class="daemon">ntpdate</systemitem> servers, using a text editor running as root, edit <filename>/etc/ntp/step-tickers</filename> to include one or more host names as follows:
-  <screen>clock1.example.com
-clock2.example.com</screen>
-The number of servers listed is not very important as <systemitem class="daemon">ntpdate</systemitem> will only use this to obtain the date information once when the system is starting. If you have an internal time server then use that host name for the first line. An additional host on the second line as a backup is sensible. The selection of backup servers and whether the second host is internal or external depends on your risk assessment. For example, what is the chance of any problem affecting the fist server also affecting the second server? Would connectivity to an external server be more likely to be available than connectivity to internal servers in the event of a network failure disrupting access to the first server?
-</para>
-
-<para>
-  The <systemitem class="daemon">ntpdate</systemitem> service has a file that must contain a list of <systemitem class="protocol">NTP</systemitem> servers to be used on system start. It is recommend to have at last four servers listed to reduce the chance of a <quote>false ticker</quote> (incorrect time source) influencing the quality of the time offset calculation. However, publicly accessible time sources are rarely incorrect.</para>
-
-</section>
-
-
 <section id="s1-Configure_NTP">
   <title>Configure NTP</title>
   <para>