<?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: FAST REBOOT in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435905#M768330</link>
    <description>Samuel,&lt;BR /&gt;&lt;BR /&gt;I have to agree with Chris. Leave fastboot off. For customer/production systems, the cost of having it spend a few minutes checking memory far outways the potential downtime of a crash caused by a memory failure.&lt;BR /&gt;&lt;BR /&gt;That said, whenever I'm setting up machines or know I'm going to be rebooting a machine a lot (even customer machines), I'll turn fastboot on. However, I always turn it off afterwards.&lt;BR /&gt;&lt;BR /&gt;Btw, I thought the N-Class memory check was pretty fast (compared to the T-Class anyway).</description>
    <pubDate>Thu, 10 Aug 2000 20:00:33 GMT</pubDate>
    <dc:creator>Andy Monks</dc:creator>
    <dc:date>2000-08-10T20:00:33Z</dc:date>
    <item>
      <title>FAST REBOOT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435902#M768327</link>
      <description>How can I do a "fast reboot" of a N-class server without the system having to go through the long memory check, etc?  Thanks.</description>
      <pubDate>Thu, 10 Aug 2000 17:14:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435902#M768327</guid>
      <dc:creator>Samuel Winful</dc:creator>
      <dc:date>2000-08-10T17:14:05Z</dc:date>
    </item>
    <item>
      <title>Re: FAST REBOOT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435903#M768328</link>
      <description>The exercise is very important for you system healthy run state.&lt;BR /&gt;</description>
      <pubDate>Thu, 10 Aug 2000 17:44:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435903#M768328</guid>
      <dc:creator>CHRIS_ANORUO</dc:creator>
      <dc:date>2000-08-10T17:44:50Z</dc:date>
    </item>
    <item>
      <title>Re: FAST REBOOT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435904#M768329</link>
      <description>Try this:&lt;BR /&gt;&lt;BR /&gt;At the IPL&lt;BR /&gt;&lt;BR /&gt;&amp;gt; CO     (configuration)&lt;BR /&gt;&amp;gt;FB  ON  (fast boot on)&lt;BR /&gt;</description>
      <pubDate>Thu, 10 Aug 2000 18:49:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435904#M768329</guid>
      <dc:creator>Kofi ARTHIABAH</dc:creator>
      <dc:date>2000-08-10T18:49:53Z</dc:date>
    </item>
    <item>
      <title>Re: FAST REBOOT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435905#M768330</link>
      <description>Samuel,&lt;BR /&gt;&lt;BR /&gt;I have to agree with Chris. Leave fastboot off. For customer/production systems, the cost of having it spend a few minutes checking memory far outways the potential downtime of a crash caused by a memory failure.&lt;BR /&gt;&lt;BR /&gt;That said, whenever I'm setting up machines or know I'm going to be rebooting a machine a lot (even customer machines), I'll turn fastboot on. However, I always turn it off afterwards.&lt;BR /&gt;&lt;BR /&gt;Btw, I thought the N-Class memory check was pretty fast (compared to the T-Class anyway).</description>
      <pubDate>Thu, 10 Aug 2000 20:00:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435905#M768330</guid>
      <dc:creator>Andy Monks</dc:creator>
      <dc:date>2000-08-10T20:00:33Z</dc:date>
    </item>
    <item>
      <title>Re: FAST REBOOT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435906#M768331</link>
      <description>Hi Samuel,&lt;BR /&gt;&lt;BR /&gt;To add to Andy's answer, it experience that counts in this business. Be on the save side of caution and learn more from your peers.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers!&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Aug 2000 07:27:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435906#M768331</guid>
      <dc:creator>CHRIS_ANORUO</dc:creator>
      <dc:date>2000-08-11T07:27:18Z</dc:date>
    </item>
    <item>
      <title>Re: FAST REBOOT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435907#M768332</link>
      <description>&lt;BR /&gt;Im afraid I have to disagree. Having FASTBOOT ON is fine in my experience. Most of the HP servers we use stay up for a long time, few reboots, so not often is a memory check after a reboot going to be run to find a problem. Instead, the diagnostic software (OnlineDiag) is running on the servers all the time continuously checking for memory errors. This should obviously then be the preferred method to detect memory problems.&lt;BR /&gt;&lt;BR /&gt;It is these daemons that detect memory errors and report them via logfiles/email warning you of bit errors and deallocations and impending memory failure requiring replacement. In my experience well into the 99% of all memory problem are picked up by the diagnostic software, not during reboots.&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Aug 2000 08:46:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fast-reboot/m-p/2435907#M768332</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2000-08-11T08:46:37Z</dc:date>
    </item>
  </channel>
</rss>

