<?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 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450843#M358652</link>
    <description>Hello, &lt;BR /&gt;&lt;BR /&gt;&amp;gt; 2 Jul 09:08:58 ntpdate[23513]: step time server 10.10.45.21 offset -288.642757 sec&lt;BR /&gt;&lt;BR /&gt;The step time message comes from ntpdate and it shows you the result of the ntpdate call (using the list in /etc/rc.config.d/netdaemons ). the message shows you that it had to adjust the time by 288 seconds to line it up with the ntp server at address 10.10.45.21. Which by the way was not one of the addresses you mentioned earlier. The start script then moves on and starts ntpd using the ntp.conf settings . &lt;BR /&gt;Regards&lt;BR /&gt;Mike</description>
    <pubDate>Thu, 02 Jul 2009 11:53:09 GMT</pubDate>
    <dc:creator>BUPA IS</dc:creator>
    <dc:date>2009-07-02T11:53:09Z</dc:date>
    <item>
      <title>ntp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450836#M358645</link>
      <description>&lt;BR /&gt;Hi admins,&lt;BR /&gt;&lt;BR /&gt;I have 2 ntp servers .primary and secondary.&lt;BR /&gt;&lt;BR /&gt;i have configured both in /etc/ntp.conf and /etc/rc.config.d/netdaemons&lt;BR /&gt;its working fine primary as master and secondery as optional(+)&lt;BR /&gt;&lt;BR /&gt;but i commented(#) primary in ntp.conf so secondary should act as master with next time sync. But it shows previous output only.when i&lt;BR /&gt;restarted xntpd it shows sec ans master.&lt;BR /&gt;&lt;BR /&gt;without restring xntpd i want secondery acts as master&lt;BR /&gt;&lt;BR /&gt;help me on this&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Jul 2009 09:55:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450836#M358645</guid>
      <dc:creator>himacs</dc:creator>
      <dc:date>2009-07-01T09:55:22Z</dc:date>
    </item>
    <item>
      <title>Re: ntp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450837#M358646</link>
      <description>Hello, &lt;BR /&gt;       The ntp client only reads the config file at startup. You can use the xntpdc command to add and remove services if you set up the ntp security keys.  Restarting ntp on a sychronised system usualy has little effect. &lt;BR /&gt;Check the offsets with ntpdate first though.   &lt;BR /&gt;&lt;BR /&gt; However there is no real concept of secondary and primary time servers. ntp works out which is the most reliable time server and chooses that as the server to synchronise the clock with.  If you only use two time sources it will flip flop between them, because it never quite knows which is correct. You should use a third one to give you a casting vote. So if two agree and one has gone wrong you still have a reliable time setting . &lt;BR /&gt;&lt;BR /&gt;I hope this helps &lt;BR /&gt;Mike</description>
      <pubDate>Wed, 01 Jul 2009 10:13:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450837#M358646</guid>
      <dc:creator>BUPA IS</dc:creator>
      <dc:date>2009-07-01T10:13:52Z</dc:date>
    </item>
    <item>
      <title>Re: ntp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450838#M358647</link>
      <description>thanx BUPA,&lt;BR /&gt;&lt;BR /&gt;my concern is if first server crashed,the second one should take care of time syncing.&lt;BR /&gt;&lt;BR /&gt;in ntp.conf and netdaemons i have mentione dboth servers&lt;BR /&gt;&lt;BR /&gt;ntp.conf&lt;BR /&gt;------&lt;BR /&gt;10.10.15.10&lt;BR /&gt;10.10.18.23&lt;BR /&gt;&lt;BR /&gt;NETDAEMONS&lt;BR /&gt;-------&lt;BR /&gt;export NTPDATE_SERVER='10.10.15.10  10.10.18.23'        &lt;BR /&gt;export XNTPD=1&lt;BR /&gt;export XNTPD_ARGS=&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;himacs&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Jul 2009 10:24:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450838#M358647</guid>
      <dc:creator>himacs</dc:creator>
      <dc:date>2009-07-01T10:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: ntp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450839#M358648</link>
      <description>hello , &lt;BR /&gt;      Your settings seem fine &lt;BR /&gt;If you look  at the output of ntpq -p  and ntpq -c rv you will see which severs are in use and which one your system is sychronised to.&lt;BR /&gt;&lt;BR /&gt;mike  &lt;BR /&gt;</description>
      <pubDate>Wed, 01 Jul 2009 10:33:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450839#M358648</guid>
      <dc:creator>BUPA IS</dc:creator>
      <dc:date>2009-07-01T10:33:02Z</dc:date>
    </item>
    <item>
      <title>Re: ntp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450840#M358649</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Your ntp setup should work as a sort of cluster.&lt;BR /&gt;&lt;BR /&gt;If both servers have access to external time sources, then if primary is gone for a while nothing bad will happen.&lt;BR /&gt;&lt;BR /&gt;The key is to configure the internal systems connecting to use both servers, then you will be fine.&lt;BR /&gt;&lt;BR /&gt;ntp was designed as an active active highly available mode of operation.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 01 Jul 2009 10:35:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450840#M358649</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-07-01T10:35:20Z</dc:date>
    </item>
    <item>
      <title>Re: ntp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450841#M358650</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;BUPA is correct.  A good setup uses at least three time sources to avoid synchronization with an "insane" timekeeper.  As NTP works you may see a different time source "promoted".  This is normal and occurs if/when NTP decides that a better source exists.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 01 Jul 2009 11:02:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450841#M358650</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-07-01T11:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: ntp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450842#M358651</link>
      <description>Thanks you all for u replies.U guided me well.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/sbin/init.d/xntpd start&lt;BR /&gt; 2 Jul 09:08:58 ntpdate[23513]: step time server 10.10.45.21 offset -288.642757 sec&lt;BR /&gt;&lt;BR /&gt;here whats step time server...whether it means secondery one..&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;himacs&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Jul 2009 04:12:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450842#M358651</guid>
      <dc:creator>himacs</dc:creator>
      <dc:date>2009-07-02T04:12:32Z</dc:date>
    </item>
    <item>
      <title>Re: ntp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450843#M358652</link>
      <description>Hello, &lt;BR /&gt;&lt;BR /&gt;&amp;gt; 2 Jul 09:08:58 ntpdate[23513]: step time server 10.10.45.21 offset -288.642757 sec&lt;BR /&gt;&lt;BR /&gt;The step time message comes from ntpdate and it shows you the result of the ntpdate call (using the list in /etc/rc.config.d/netdaemons ). the message shows you that it had to adjust the time by 288 seconds to line it up with the ntp server at address 10.10.45.21. Which by the way was not one of the addresses you mentioned earlier. The start script then moves on and starts ntpd using the ntp.conf settings . &lt;BR /&gt;Regards&lt;BR /&gt;Mike</description>
      <pubDate>Thu, 02 Jul 2009 11:53:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp/m-p/4450843#M358652</guid>
      <dc:creator>BUPA IS</dc:creator>
      <dc:date>2009-07-02T11:53:09Z</dc:date>
    </item>
  </channel>
</rss>

