<?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: System clock error in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040162#M6005</link>
    <description>It seems that your problem is lasting since&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xacc568da2286d711abdc0090277a778c,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xacc568da2286d711abdc0090277a778c,00.html&lt;/A&gt;&lt;BR /&gt;It may be a hardware issue... So best solution would be ntp, as suggested (apart from changing BIOS battery).&lt;BR /&gt;&lt;BR /&gt;Don't forget also that system tries to synchronise on reboot hardware time and system time, if one makes problem, then it may influence the other (kind of set time = time +1s process running somewhere). You mayn search for long before finding it... Try to observe anyway if this run happens during machine working time, machine idle time, or reboot...&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;J</description>
    <pubDate>Mon, 04 Aug 2003 11:05:15 GMT</pubDate>
    <dc:creator>Jerome Henry</dc:creator>
    <dc:date>2003-08-04T11:05:15Z</dc:date>
    <item>
      <title>System clock error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040159#M6002</link>
      <description>I run RH8 on my server , the system clock always run faster than normal ( about 10 minutes per week ) , how can I fix it ? thx</description>
      <pubDate>Mon, 04 Aug 2003 05:03:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040159#M6002</guid>
      <dc:creator>juno2</dc:creator>
      <dc:date>2003-08-04T05:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: System clock error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040160#M6003</link>
      <description>check &lt;A href="http://users.dslextreme.com/~craig.lawson/linux_notes/clock.html#manual_assessment_of_drift" target="_blank"&gt;http://users.dslextreme.com/~craig.lawson/linux_notes/clock.html#manual_assessment_of_drift&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;Manual Drift Assessment for the Hardware Clock &lt;BR /&gt;&lt;BR /&gt;I hope it'll help you.&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;Vitaly</description>
      <pubDate>Mon, 04 Aug 2003 06:38:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040160#M6003</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2003-08-04T06:38:39Z</dc:date>
    </item>
    <item>
      <title>Re: System clock error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040161#M6004</link>
      <description>Better yet, rely on accurate time sources. Use NTP.&lt;BR /&gt;&lt;BR /&gt;See &lt;A href="http://www.tldp.org/HOWTO/TimePrecision-HOWTO/ntp.html" target="_blank"&gt;http://www.tldp.org/HOWTO/TimePrecision-HOWTO/ntp.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Cristi</description>
      <pubDate>Mon, 04 Aug 2003 08:11:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040161#M6004</guid>
      <dc:creator>Cristian Draghici_1</dc:creator>
      <dc:date>2003-08-04T08:11:06Z</dc:date>
    </item>
    <item>
      <title>Re: System clock error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040162#M6005</link>
      <description>It seems that your problem is lasting since&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xacc568da2286d711abdc0090277a778c,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xacc568da2286d711abdc0090277a778c,00.html&lt;/A&gt;&lt;BR /&gt;It may be a hardware issue... So best solution would be ntp, as suggested (apart from changing BIOS battery).&lt;BR /&gt;&lt;BR /&gt;Don't forget also that system tries to synchronise on reboot hardware time and system time, if one makes problem, then it may influence the other (kind of set time = time +1s process running somewhere). You mayn search for long before finding it... Try to observe anyway if this run happens during machine working time, machine idle time, or reboot...&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;J</description>
      <pubDate>Mon, 04 Aug 2003 11:05:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040162#M6005</guid>
      <dc:creator>Jerome Henry</dc:creator>
      <dc:date>2003-08-04T11:05:15Z</dc:date>
    </item>
    <item>
      <title>Re: System clock error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040163#M6006</link>
      <description>My HP-UX boxes gain or lose 15 minutes a week if they aren't configured with ntp.  One of mine once thought it was next week.&lt;BR /&gt;&lt;BR /&gt;The real problem is that the ntp port is blocked on most networks.  The second problem is the standard ntpd server that ships with Windows is NOT unix compliant.&lt;BR /&gt;&lt;BR /&gt;If the port is open, use the links below to pick a time server.  There is a good ntp client/server for nt in these links as well.&lt;BR /&gt;&lt;BR /&gt;ntp was INVENTED by Dr. David Mills and I'm putting in his web site too.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.eecis.udel.edu/~mills/" target="_blank"&gt;http://www.eecis.udel.edu/~mills/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.ntp.org/documentation.html" target="_blank"&gt;http://www.ntp.org/documentation.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://developer.novell.com/research/appnotes/1999/july/03/02.htm" target="_blank"&gt;http://developer.novell.com/research/appnotes/1999/july/03/02.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.tymserve.com/success_tva.html" target="_blank"&gt;http://www.tymserve.com/success_tva.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.endruntechnologies.com/ntp.htm" target="_blank"&gt;http://www.endruntechnologies.com/ntp.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 04 Aug 2003 12:02:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040163#M6006</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-08-04T12:02:25Z</dc:date>
    </item>
    <item>
      <title>Re: System clock error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040164#M6007</link>
      <description>Perhaps, if you have more then one Unix on your lan You could set one that run's accuratly as an ntp server and the lazy one as a client ?&lt;BR /&gt;&lt;BR /&gt;just my 2 cent worth&lt;BR /&gt;&lt;BR /&gt;As stated above a check to motherboard battery could also help&lt;BR /&gt;&lt;BR /&gt;Jean-Pierre</description>
      <pubDate>Tue, 05 Aug 2003 12:29:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-clock-error/m-p/3040164#M6007</guid>
      <dc:creator>Huc_1</dc:creator>
      <dc:date>2003-08-05T12:29:52Z</dc:date>
    </item>
  </channel>
</rss>

