<?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: hpterm malloc failed in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/hpterm-malloc-failed/m-p/4904100#M404669</link>
    <description>Both xterm and hpterm require first-in-first-out pty (pseudo-terminal) devices. These legacy pty devices are controlled by 2 factors: the size of the device table in the kernel (npty variable) and the device files themselves. I'm wondering if you have therefor run out of npty's ?&lt;BR /&gt;&lt;BR /&gt;Qu does xterm also fail but dtterm work by any chance ?&lt;BR /&gt;&lt;BR /&gt;To increase the number of available pty devices, it is neccessary to increase the kernel parameter "npty" to the desired level and create additional pty devices with the following commands: &lt;BR /&gt;&lt;BR /&gt;insf -e &lt;BR /&gt;&lt;BR /&gt;then&lt;BR /&gt;&lt;BR /&gt;insf -d &lt;DRIVER&gt; -n #npty's &lt;BR /&gt;&lt;BR /&gt;&lt;/DRIVER&gt;</description>
    <pubDate>Thu, 26 May 2005 10:29:57 GMT</pubDate>
    <dc:creator>Alex Glennie</dc:creator>
    <dc:date>2005-05-26T10:29:57Z</dc:date>
    <item>
      <title>hpterm malloc failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpterm-malloc-failed/m-p/4904098#M404667</link>
      <description>I have an HP B.10.20 system that is getting the error "hpterm: malloc failed(34)" whenever I try to start hpterm.  I attempted to copy a known good copy from another system that is at the same patch level.  I still get the same error.  I compared /usr/lib/X11/app-defaults/HPterm files on both and they are identical.  Does anyone have any suggestions on finding the cause?</description>
      <pubDate>Thu, 26 May 2005 10:10:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpterm-malloc-failed/m-p/4904098#M404667</guid>
      <dc:creator>CSG Office</dc:creator>
      <dc:date>2005-05-26T10:10:25Z</dc:date>
    </item>
    <item>
      <title>Re: hpterm malloc failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpterm-malloc-failed/m-p/4904099#M404668</link>
      <description>I suspect that you need to increase maxdsiz and build a new kernel. You could also have insufficent swap space.</description>
      <pubDate>Thu, 26 May 2005 10:26:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpterm-malloc-failed/m-p/4904099#M404668</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-05-26T10:26:06Z</dc:date>
    </item>
    <item>
      <title>Re: hpterm malloc failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpterm-malloc-failed/m-p/4904100#M404669</link>
      <description>Both xterm and hpterm require first-in-first-out pty (pseudo-terminal) devices. These legacy pty devices are controlled by 2 factors: the size of the device table in the kernel (npty variable) and the device files themselves. I'm wondering if you have therefor run out of npty's ?&lt;BR /&gt;&lt;BR /&gt;Qu does xterm also fail but dtterm work by any chance ?&lt;BR /&gt;&lt;BR /&gt;To increase the number of available pty devices, it is neccessary to increase the kernel parameter "npty" to the desired level and create additional pty devices with the following commands: &lt;BR /&gt;&lt;BR /&gt;insf -e &lt;BR /&gt;&lt;BR /&gt;then&lt;BR /&gt;&lt;BR /&gt;insf -d &lt;DRIVER&gt; -n #npty's &lt;BR /&gt;&lt;BR /&gt;&lt;/DRIVER&gt;</description>
      <pubDate>Thu, 26 May 2005 10:29:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpterm-malloc-failed/m-p/4904100#M404669</guid>
      <dc:creator>Alex Glennie</dc:creator>
      <dc:date>2005-05-26T10:29:57Z</dc:date>
    </item>
    <item>
      <title>Re: hpterm malloc failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpterm-malloc-failed/m-p/4904101#M404670</link>
      <description>Thanks guys.  Pointing to a resource limit made me double check all of the processes running.  There were about 100 processes that were running that needed killed.</description>
      <pubDate>Thu, 26 May 2005 11:51:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpterm-malloc-failed/m-p/4904101#M404670</guid>
      <dc:creator>CSG Office</dc:creator>
      <dc:date>2005-05-26T11:51:50Z</dc:date>
    </item>
    <item>
      <title>Re: hpterm malloc failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpterm-malloc-failed/m-p/4904102#M404671</link>
      <description>Closing.</description>
      <pubDate>Thu, 26 May 2005 11:52:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpterm-malloc-failed/m-p/4904102#M404671</guid>
      <dc:creator>CSG Office</dc:creator>
      <dc:date>2005-05-26T11:52:48Z</dc:date>
    </item>
  </channel>
</rss>

