<?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 spawning to rapidly in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/spawning-to-rapidly/m-p/4051229#M304530</link>
    <description>I just ignited a tape from our production box hp L2000 with unix version 11.11.  I ignited VG00 which contains the volume groups:  /, /stand, /var, /tmp, /opt, /home.&lt;BR /&gt;&lt;BR /&gt;During the reboot process i had to interrupt the process so i can reboot from the ignite tape.  I then had to install unix, change the ip address.  It then archived the information from the boot up tape (ignite tape) and continued on.  Once it finished it will give me a spawning to rapidly message.  I then went into the production box and looked at the /etc/inittab file and noticed that the following lines were the ones giving me the problems.  (I noticed they were not commented out on the production box.)  I also wanted to know what are the repercussions of commenting out these lines on the production box.&lt;BR /&gt;&lt;BR /&gt;samd:23456:respawn:/usr/sam/lbin/cimserverd&lt;BR /&gt;cons:123456:respawn:/usr/sbin/getty console console        #system console&lt;BR /&gt;ems4:3456:respawn:/etc/opt/resmon/lbin/p_client&lt;BR /&gt;&lt;BR /&gt;The console is a dummy terminal directly attached to the back of the coop box server.</description>
    <pubDate>Tue, 07 Aug 2007 10:49:03 GMT</pubDate>
    <dc:creator>keith demingware</dc:creator>
    <dc:date>2007-08-07T10:49:03Z</dc:date>
    <item>
      <title>spawning to rapidly</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spawning-to-rapidly/m-p/4051229#M304530</link>
      <description>I just ignited a tape from our production box hp L2000 with unix version 11.11.  I ignited VG00 which contains the volume groups:  /, /stand, /var, /tmp, /opt, /home.&lt;BR /&gt;&lt;BR /&gt;During the reboot process i had to interrupt the process so i can reboot from the ignite tape.  I then had to install unix, change the ip address.  It then archived the information from the boot up tape (ignite tape) and continued on.  Once it finished it will give me a spawning to rapidly message.  I then went into the production box and looked at the /etc/inittab file and noticed that the following lines were the ones giving me the problems.  (I noticed they were not commented out on the production box.)  I also wanted to know what are the repercussions of commenting out these lines on the production box.&lt;BR /&gt;&lt;BR /&gt;samd:23456:respawn:/usr/sam/lbin/cimserverd&lt;BR /&gt;cons:123456:respawn:/usr/sbin/getty console console        #system console&lt;BR /&gt;ems4:3456:respawn:/etc/opt/resmon/lbin/p_client&lt;BR /&gt;&lt;BR /&gt;The console is a dummy terminal directly attached to the back of the coop box server.</description>
      <pubDate>Tue, 07 Aug 2007 10:49:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spawning-to-rapidly/m-p/4051229#M304530</guid>
      <dc:creator>keith demingware</dc:creator>
      <dc:date>2007-08-07T10:49:03Z</dc:date>
    </item>
    <item>
      <title>Re: spawning to rapidly</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spawning-to-rapidly/m-p/4051230#M304531</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Start out with the working /etc/inittab from production and add what additional fucntionality the second system requires. This should solve and avoid the problem.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 07 Aug 2007 10:55:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spawning-to-rapidly/m-p/4051230#M304531</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-08-07T10:55:33Z</dc:date>
    </item>
    <item>
      <title>Re: spawning to rapidly</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spawning-to-rapidly/m-p/4051231#M304532</link>
      <description>Hi&lt;BR /&gt;You may want to check /etc/fstab if there is any entry of filesystem from non-vg00. If so, just comment it out.</description>
      <pubDate>Wed, 08 Aug 2007 21:23:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spawning-to-rapidly/m-p/4051231#M304532</guid>
      <dc:creator>Haniza</dc:creator>
      <dc:date>2007-08-08T21:23:10Z</dc:date>
    </item>
    <item>
      <title>Re: spawning to rapidly</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spawning-to-rapidly/m-p/4051232#M304533</link>
      <description>cons:123456:respawn:/usr/sbin/getty console console #system console&lt;BR /&gt;&lt;BR /&gt;this line is to allow login to the console. commenting this will later cause the console unable to login.</description>
      <pubDate>Wed, 08 Aug 2007 21:30:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spawning-to-rapidly/m-p/4051232#M304533</guid>
      <dc:creator>tkc</dc:creator>
      <dc:date>2007-08-08T21:30:39Z</dc:date>
    </item>
  </channel>
</rss>

