<?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 NPar uptime in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/npar-uptime/m-p/4548658#M370324</link>
    <description>Does anyone know a way to determine the uptime of an NPar when it is running VPars?  We have some NPars that have been running a very long time where the VPars have been rebooted regularly but I don't believe that the NPar has actually been cycled since 1970.  &lt;BR /&gt;Is it really helpful or valuable to ever boot an NPar since it would really only be a cycle of vpmon?&lt;BR /&gt;How long do people normally run an NPar between boots (where the NPar runs VPars which are booted regularly).&lt;BR /&gt;Appreciate any input</description>
    <pubDate>Fri, 11 Dec 2009 19:27:08 GMT</pubDate>
    <dc:creator>Dana IT Unix Sysmgt.Tea</dc:creator>
    <dc:date>2009-12-11T19:27:08Z</dc:date>
    <item>
      <title>NPar uptime</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/npar-uptime/m-p/4548658#M370324</link>
      <description>Does anyone know a way to determine the uptime of an NPar when it is running VPars?  We have some NPars that have been running a very long time where the VPars have been rebooted regularly but I don't believe that the NPar has actually been cycled since 1970.  &lt;BR /&gt;Is it really helpful or valuable to ever boot an NPar since it would really only be a cycle of vpmon?&lt;BR /&gt;How long do people normally run an NPar between boots (where the NPar runs VPars which are booted regularly).&lt;BR /&gt;Appreciate any input</description>
      <pubDate>Fri, 11 Dec 2009 19:27:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/npar-uptime/m-p/4548658#M370324</guid>
      <dc:creator>Dana IT Unix Sysmgt.Tea</dc:creator>
      <dc:date>2009-12-11T19:27:08Z</dc:date>
    </item>
    <item>
      <title>Re: NPar uptime</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/npar-uptime/m-p/4548659#M370325</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Go through the console log&lt;BR /&gt;&lt;BR /&gt;Javed</description>
      <pubDate>Sat, 12 Dec 2009 11:37:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/npar-uptime/m-p/4548659#M370325</guid>
      <dc:creator>Javed Khan_1</dc:creator>
      <dc:date>2009-12-12T11:37:35Z</dc:date>
    </item>
    <item>
      <title>Re: NPar uptime</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/npar-uptime/m-p/4548660#M370326</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Why wouldn't the uptime from the Npar O/S command line be what you want?&lt;BR /&gt;&lt;BR /&gt;I managed 5 Superdomes and they stayed up for years and we didn't worry about.&lt;BR /&gt;&lt;BR /&gt;Unless you see a problem, then don't worry about it unless you want the training and to review the procedure, then its a good thing.  Find the time to do it if you never have.</description>
      <pubDate>Sat, 12 Dec 2009 14:51:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/npar-uptime/m-p/4548660#M370326</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2009-12-12T14:51:55Z</dc:date>
    </item>
    <item>
      <title>Re: NPar uptime</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/npar-uptime/m-p/4548661#M370327</link>
      <description>IMHO there is a small chance to find boot related entries in MP log, But since this is a FIFO, this information may be already gone.&lt;BR /&gt;&lt;BR /&gt;Same for "vparstatus -e".&lt;BR /&gt;&lt;BR /&gt;But who cares and why?&lt;BR /&gt;&lt;BR /&gt;;-)</description>
      <pubDate>Mon, 14 Dec 2009 14:06:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/npar-uptime/m-p/4548661#M370327</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-12-14T14:06:32Z</dc:date>
    </item>
    <item>
      <title>Re: NPar uptime</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/npar-uptime/m-p/4548662#M370328</link>
      <description>Zero pointed my response.&lt;BR /&gt;&lt;BR /&gt;We were kind of wondering on Friday how long our npars have been running and could not come up with a good answer.&lt;BR /&gt;&lt;BR /&gt;We have a schedule to make sure vpars get booted every month and are wondering if people regularly boot npars or not. Its a pretty simple setup and not likely to get a memory leak, but can it run forever without a reboot?&lt;BR /&gt;&lt;BR /&gt;I've requested HP delete the SEP response.&lt;BR /&gt;&lt;BR /&gt;SEP&lt;BR /&gt;</description>
      <pubDate>Mon, 14 Dec 2009 14:06:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/npar-uptime/m-p/4548662#M370328</guid>
      <dc:creator>Dana IT Unix Sysmgt.Tea</dc:creator>
      <dc:date>2009-12-14T14:06:53Z</dc:date>
    </item>
  </channel>
</rss>

