<?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: time went bad if ntp server down in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/time-went-bad-if-ntp-server-down/m-p/4442753#M37111</link>
    <description>Dear Colin Topliss, Thanks for excellent help ;)&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Maaz</description>
    <pubDate>Fri, 19 Jun 2009 04:41:27 GMT</pubDate>
    <dc:creator>Maaz</dc:creator>
    <dc:date>2009-06-19T04:41:27Z</dc:date>
    <item>
      <title>time went bad if ntp server down</title>
      <link>https://community.hpe.com/t5/operating-system-linux/time-went-bad-if-ntp-server-down/m-p/4442751#M37109</link>
      <description>during system startup/boot, whenever the ntp server is not available/accessible, the date/time on my SUSE 10 ntp client machines became bad/wrong...&lt;BR /&gt;&lt;BR /&gt;e.g when today I reboot my machine at 17:01 GMT-6 and ntp server was not available/accessible, the time on my machine went/became bad&lt;BR /&gt;# date &lt;BR /&gt;Mon Jun 15 15:04:28 GMT-6 2009&lt;BR /&gt;&lt;BR /&gt;while originally it was &lt;BR /&gt;Wed Jun 17 07:02:15 GMT-6 2009&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;but my windows boxes remains on proper time, if ntp server is not available/accessible during the system startup/boot.&lt;BR /&gt;&lt;BR /&gt;How can I configure my Linux boxes to retain the right/proper time, if NTP server not available ?</description>
      <pubDate>Thu, 18 Jun 2009 18:18:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/time-went-bad-if-ntp-server-down/m-p/4442751#M37109</guid>
      <dc:creator>Maaz</dc:creator>
      <dc:date>2009-06-18T18:18:11Z</dc:date>
    </item>
    <item>
      <title>Re: time went bad if ntp server down</title>
      <link>https://community.hpe.com/t5/operating-system-linux/time-went-bad-if-ntp-server-down/m-p/4442752#M37110</link>
      <description>It could be that its taken the time from the CMOS. That then could have put the time out far enough to stop NTP from syncing properly.&lt;BR /&gt;&lt;BR /&gt;Try changing&lt;BR /&gt;&lt;BR /&gt;NTPD_ADJUST_CMOS_CLOCK="no"&lt;BR /&gt;&lt;BR /&gt;to &lt;BR /&gt;&lt;BR /&gt;NTPD_ADJUST_CMOS_CLOCK="yes"&lt;BR /&gt;&lt;BR /&gt;in /etc/sysconfig/ntp. You might find that helps keep the time in sync.&lt;BR /&gt;&lt;BR /&gt;Colin</description>
      <pubDate>Thu, 18 Jun 2009 19:30:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/time-went-bad-if-ntp-server-down/m-p/4442752#M37110</guid>
      <dc:creator>Colin Topliss</dc:creator>
      <dc:date>2009-06-18T19:30:30Z</dc:date>
    </item>
    <item>
      <title>Re: time went bad if ntp server down</title>
      <link>https://community.hpe.com/t5/operating-system-linux/time-went-bad-if-ntp-server-down/m-p/4442753#M37111</link>
      <description>Dear Colin Topliss, Thanks for excellent help ;)&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Maaz</description>
      <pubDate>Fri, 19 Jun 2009 04:41:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/time-went-bad-if-ntp-server-down/m-p/4442753#M37111</guid>
      <dc:creator>Maaz</dc:creator>
      <dc:date>2009-06-19T04:41:27Z</dc:date>
    </item>
  </channel>
</rss>

