<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic NTP Client configuration in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-client-configuration/m-p/2513467#M22508</link>
    <description>What happens if my NTPDATE_SERVER is down (in etc/rc.config.d/netdaemons) when my NTP client server is rebooted?  Will the NTP client know what time it is?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;..Joe</description>
    <pubDate>Wed, 04 Apr 2001 13:56:52 GMT</pubDate>
    <dc:creator>Joe Profaizer</dc:creator>
    <dc:date>2001-04-04T13:56:52Z</dc:date>
    <item>
      <title>NTP Client configuration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-client-configuration/m-p/2513467#M22508</link>
      <description>What happens if my NTPDATE_SERVER is down (in etc/rc.config.d/netdaemons) when my NTP client server is rebooted?  Will the NTP client know what time it is?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;..Joe</description>
      <pubDate>Wed, 04 Apr 2001 13:56:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp-client-configuration/m-p/2513467#M22508</guid>
      <dc:creator>Joe Profaizer</dc:creator>
      <dc:date>2001-04-04T13:56:52Z</dc:date>
    </item>
    <item>
      <title>Re: NTP Client configuration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-client-configuration/m-p/2513468#M22509</link>
      <description>It will error when trying to set the date via ntpdate, but it will go according to the internal clock.  If you have ntpd running, it will sync when the machine comes back up.</description>
      <pubDate>Wed, 04 Apr 2001 14:01:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp-client-configuration/m-p/2513468#M22509</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2001-04-04T14:01:30Z</dc:date>
    </item>
    <item>
      <title>Re: NTP Client configuration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-client-configuration/m-p/2513469#M22510</link>
      <description>NTPDATE_SERVER is for the sync,if it is down you have in /var/adm/syslog/syslog.log messages of lost sync.</description>
      <pubDate>Wed, 04 Apr 2001 14:02:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp-client-configuration/m-p/2513469#M22510</guid>
      <dc:creator>Vincenzo Restuccia</dc:creator>
      <dc:date>2001-04-04T14:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: NTP Client configuration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-client-configuration/m-p/2513470#M22511</link>
      <description>You can also set up multiple NTP servers so that at least one of them is up.&lt;BR /&gt;&lt;BR /&gt;My sync with NTP happens about once an hour and is in microseconds increments.  It will not matter much if the time server can't be found for even a few days unless you have an application that depends on this accuracy.</description>
      <pubDate>Wed, 04 Apr 2001 14:54:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp-client-configuration/m-p/2513470#M22511</guid>
      <dc:creator>John Bolene</dc:creator>
      <dc:date>2001-04-04T14:54:40Z</dc:date>
    </item>
  </channel>
</rss>

