<?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: Wrong date and time in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464698#M848950</link>
    <description>If you don't have the money to fix the problem (which should be cheap considering the gray and used market), I'd suggest running ntp and syncing the clock at each boot. The problem here is that if you have time/date sensitive data written to the computer you may be in trouble.</description>
    <pubDate>Tue, 18 Jan 2005 15:10:03 GMT</pubDate>
    <dc:creator>Peyman Javaheri</dc:creator>
    <dc:date>2005-01-18T15:10:03Z</dc:date>
    <item>
      <title>Wrong date and time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464693#M848945</link>
      <description>AFTER OF ONE REBOOT THE DATE AND HOUR OF MY  K370 CHANGE OF JANUARY 10 2005 TO DECEMBER 20 2004, DOES SOMEBODY KNOW THAT REASON can HAVE FOR THIS?</description>
      <pubDate>Mon, 17 Jan 2005 13:08:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464693#M848945</guid>
      <dc:creator>Alberto Hurtado</dc:creator>
      <dc:date>2005-01-17T13:08:36Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong date and time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464694#M848946</link>
      <description>Why did you reboot?&lt;BR /&gt;&lt;BR /&gt;Maybe something happend prior to reboot...&lt;BR /&gt;&lt;BR /&gt;Did you reboot - or power off?&lt;BR /&gt;&lt;BR /&gt;As part of standard operationg procedures, I always check the date/time after a reboot - prior to satrting applications.&lt;BR /&gt;&lt;BR /&gt;A K370 is quite old - maybe the battery for internal clock is getting weak?&lt;BR /&gt;&lt;BR /&gt;I'd place a support call with HP (if your server is under contract).&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Mon, 17 Jan 2005 13:20:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464694#M848946</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-01-17T13:20:20Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong date and time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464695#M848947</link>
      <description>the reason of the reboot was a general failure of power.</description>
      <pubDate>Mon, 17 Jan 2005 13:32:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464695#M848947</guid>
      <dc:creator>Alberto Hurtado</dc:creator>
      <dc:date>2005-01-17T13:32:30Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong date and time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464696#M848948</link>
      <description>You may have a dead processor battery. When the system reboots, HP-UX obtains the current time/date from the free-running clock in the processor which is always on. But if the battery is almost dead, the time/date value may be corrupted. There may also be a firmware patch for really old processors to handle problems with the hardware clock during a power fail.</description>
      <pubDate>Mon, 17 Jan 2005 15:20:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464696#M848948</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-01-17T15:20:11Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong date and time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464697#M848949</link>
      <description>Thank you, thank you very much, in fact this k370 is old, a new firmware and the quality pack (software) from a lot of time behind that they don't arrive to this server. My company don't have money for IT.</description>
      <pubDate>Mon, 17 Jan 2005 18:10:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464697#M848949</guid>
      <dc:creator>Alberto Hurtado</dc:creator>
      <dc:date>2005-01-17T18:10:42Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong date and time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464698#M848950</link>
      <description>If you don't have the money to fix the problem (which should be cheap considering the gray and used market), I'd suggest running ntp and syncing the clock at each boot. The problem here is that if you have time/date sensitive data written to the computer you may be in trouble.</description>
      <pubDate>Tue, 18 Jan 2005 15:10:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wrong-date-and-time/m-p/3464698#M848950</guid>
      <dc:creator>Peyman Javaheri</dc:creator>
      <dc:date>2005-01-18T15:10:03Z</dc:date>
    </item>
  </channel>
</rss>

