<?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 Re: NTP deamon problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-deamon-problem/m-p/3102737#M147208</link>
    <description>Always look in /var/adm/syslog/syslog.log to see what happened when the daemon was started. The start command first runs ntpdate which will JUMP the time (never good when a database is running) then start xntpd. Use ntpq to determine if all your time servers are working OK as in:&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;ntpq -p</description>
    <pubDate>Mon, 27 Oct 2003 12:40:26 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2003-10-27T12:40:26Z</dc:date>
    <item>
      <title>NTP deamon problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-deamon-problem/m-p/3102734#M147205</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;In one of my client the NTP deamon does not start. when i issue start command it sets the time but after that the deamon disappears.&lt;BR /&gt;&lt;BR /&gt;What can be the reason.</description>
      <pubDate>Mon, 27 Oct 2003 05:34:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp-deamon-problem/m-p/3102734#M147205</guid>
      <dc:creator>M. Tariq Ayub</dc:creator>
      <dc:date>2003-10-27T05:34:42Z</dc:date>
    </item>
    <item>
      <title>Re: NTP deamon problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-deamon-problem/m-p/3102735#M147206</link>
      <description>Usually this is a result of hte time difference between hte client and server being too great to be able to correct. Try setting the client time as close as possible to hte server time before starting ntp</description>
      <pubDate>Mon, 27 Oct 2003 05:44:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp-deamon-problem/m-p/3102735#M147206</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2003-10-27T05:44:15Z</dc:date>
    </item>
    <item>
      <title>Re: NTP deamon problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-deamon-problem/m-p/3102736#M147207</link>
      <description>If the /sbin/init.d/xntpd start is actually setting the time correctly this indicates that the /etc/rc.confid.d/netdaemons is correct so I would check your /etc/ntp.conf file and also permissions on /etc/ntp.key and /etc/ntp.drift.</description>
      <pubDate>Mon, 27 Oct 2003 12:24:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp-deamon-problem/m-p/3102736#M147207</guid>
      <dc:creator>John Waller</dc:creator>
      <dc:date>2003-10-27T12:24:11Z</dc:date>
    </item>
    <item>
      <title>Re: NTP deamon problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-deamon-problem/m-p/3102737#M147208</link>
      <description>Always look in /var/adm/syslog/syslog.log to see what happened when the daemon was started. The start command first runs ntpdate which will JUMP the time (never good when a database is running) then start xntpd. Use ntpq to determine if all your time servers are working OK as in:&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;ntpq -p</description>
      <pubDate>Mon, 27 Oct 2003 12:40:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp-deamon-problem/m-p/3102737#M147208</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2003-10-27T12:40:26Z</dc:date>
    </item>
  </channel>
</rss>

