<?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: ssh pseudo-terminal allocation in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277539#M474010</link>
    <description>Fred,&lt;BR /&gt;&lt;BR /&gt;you could also comment out that line in the prng file.. or change it to last -100 or something to keep it from happening again down the road.&lt;BR /&gt;&lt;BR /&gt;i believe this is used for encryption entropy, to simply generate cpu randomness.&lt;BR /&gt;&lt;BR /&gt;there are probably better ways but sometimes it is not worth the extra effort.&lt;BR /&gt;&lt;BR /&gt;glad I could help.</description>
    <pubDate>Thu, 24 Mar 2011 15:54:56 GMT</pubDate>
    <dc:creator>Tim Nelson</dc:creator>
    <dc:date>2011-03-24T15:54:56Z</dc:date>
    <item>
      <title>ssh pseudo-terminal allocation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277533#M474004</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I have ssh connexion issues on a HP-UX 11iv3 server. When connecting to this server, I have huge delays after password validation. I've verified and setup DNS correctly. But from anywhere, even from the server itself an ssh connection to this server takes lots of time. Once connected, usage is at normal speed. I've noticed that when I don't allocate a pseudo terminal (for instance by submiting command on ssh command line) connexion is not slow. So... where does this strange issue comes from ?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Fred</description>
      <pubDate>Wed, 23 Mar 2011 17:30:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277533#M474004</guid>
      <dc:creator>Fred Ruffet</dc:creator>
      <dc:date>2011-03-23T17:30:57Z</dc:date>
    </item>
    <item>
      <title>Re: ssh pseudo-terminal allocation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277534#M474005</link>
      <description>check out /opt/ssh/etc/ssh_prng_cmds&lt;BR /&gt;&lt;BR /&gt;do some timex on each command and/or write a script to process them.&lt;BR /&gt;&lt;BR /&gt;I typically see the last command slowing things down due to a large /var/adm/wtmp* files.&lt;BR /&gt;&lt;BR /&gt;or just clean out your wtmp and login again to see if that is the issue.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Mar 2011 19:20:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277534#M474005</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2011-03-23T19:20:22Z</dc:date>
    </item>
    <item>
      <title>Re: ssh pseudo-terminal allocation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277535#M474006</link>
      <description>&lt;!--!*#--&gt;&amp;gt; [...] I've verified and setup DNS&lt;BR /&gt;&amp;gt; correctly. [...]&lt;BR /&gt;&lt;BR /&gt;Your opinion, while interesting, has a value&lt;BR /&gt;which is uncertain, because only you know how&lt;BR /&gt;you set up and/or verified anything.  Many&lt;BR /&gt;people who have the usual DNS problem make&lt;BR /&gt;the same claim, and they're wrong.&lt;BR /&gt;&lt;BR /&gt;A Forum search for, say,&lt;BR /&gt;      slow ssh&lt;BR /&gt;or&lt;BR /&gt;      slow telnet&lt;BR /&gt;(or similar) should find many old threads&lt;BR /&gt;which would illustrate this.&lt;BR /&gt;&lt;BR /&gt;However, if you can get a prompt result from&lt;BR /&gt;a command like the following, when it's run&lt;BR /&gt;on the server, then you may be right, and the&lt;BR /&gt;problem may lie elsewhere.&lt;BR /&gt;&lt;BR /&gt;      nslookup &lt;CLIENT_IP_ADDRESS&gt;&lt;BR /&gt;&lt;BR /&gt;But trusting the opinions of people who ask&lt;BR /&gt;questions here, and who offer no evidence to&lt;BR /&gt;support those opinions, is often a mistake.&lt;/CLIENT_IP_ADDRESS&gt;</description>
      <pubDate>Thu, 24 Mar 2011 06:12:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277535#M474006</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2011-03-24T06:12:16Z</dc:date>
    </item>
    <item>
      <title>Re: ssh pseudo-terminal allocation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277536#M474007</link>
      <description>Steven,&lt;BR /&gt;&lt;BR /&gt;You're right that I haven't been precise enough. I've been solving this exact problem of DNS with many people telling me it was configured.&lt;BR /&gt;&lt;BR /&gt;I have nslookup working on both servers for resolution and reverse. It wasn't the case when I got on that case, but now it works. But ssh is still slow and that's why I came here. I'm truly sorry I haven't been more explicit about that.&lt;BR /&gt;&lt;BR /&gt;Problem with forums (or support in general) is always that you don't exactly know what level of knowledge others have and what they really have done.&lt;BR /&gt;&lt;BR /&gt;I will try Tim's proposition which seems particularly interesting and I'll give feed back.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Fred&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 24 Mar 2011 08:45:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277536#M474007</guid>
      <dc:creator>Fred Ruffet</dc:creator>
      <dc:date>2011-03-24T08:45:45Z</dc:date>
    </item>
    <item>
      <title>Re: ssh pseudo-terminal allocation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277537#M474008</link>
      <description>So many thanks Tim :)&lt;BR /&gt;&lt;BR /&gt;"last" is part of the commands. "timex last" returns &lt;BR /&gt;real     5:55.78&lt;BR /&gt;user        3.58&lt;BR /&gt;sys         8.49&lt;BR /&gt;and "du -k /var/adm/wtmps"&lt;BR /&gt;706728  /var/adm/wtmps&lt;BR /&gt;&lt;BR /&gt;I have trimed /var/adm/wtmps and now connection has no delay.&lt;BR /&gt;&lt;BR /&gt;Thanks again,&lt;BR /&gt;&lt;BR /&gt;Fred</description>
      <pubDate>Thu, 24 Mar 2011 09:42:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277537#M474008</guid>
      <dc:creator>Fred Ruffet</dc:creator>
      <dc:date>2011-03-24T09:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: ssh pseudo-terminal allocation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277538#M474009</link>
      <description>Problem is solved by trimming /var/tmp/wtmps. This has been done this way :&lt;BR /&gt;&lt;BR /&gt;/usr/lib/acct/fwtmp -X  /var/adm/wtmps.20110324&lt;BR /&gt;tail -100 /var/adm/wtmps.20110324 &amp;gt; /var/adm/wtmps.20110324.new&lt;BR /&gt;/usr/lib/acct/fwtmp -icX &amp;lt; /var/adm/wtmps.20110324.new &amp;gt; /var/adm/wtmps&lt;BR /&gt;gzip -9 /var/adm/wtmps.20110324&lt;BR /&gt;rm /var/adm/wtmps.20110324.new&lt;BR /&gt;&lt;BR /&gt;Thanks again to Tim&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Fred</description>
      <pubDate>Thu, 24 Mar 2011 09:43:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277538#M474009</guid>
      <dc:creator>Fred Ruffet</dc:creator>
      <dc:date>2011-03-24T09:43:49Z</dc:date>
    </item>
    <item>
      <title>Re: ssh pseudo-terminal allocation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277539#M474010</link>
      <description>Fred,&lt;BR /&gt;&lt;BR /&gt;you could also comment out that line in the prng file.. or change it to last -100 or something to keep it from happening again down the road.&lt;BR /&gt;&lt;BR /&gt;i believe this is used for encryption entropy, to simply generate cpu randomness.&lt;BR /&gt;&lt;BR /&gt;there are probably better ways but sometimes it is not worth the extra effort.&lt;BR /&gt;&lt;BR /&gt;glad I could help.</description>
      <pubDate>Thu, 24 Mar 2011 15:54:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-pseudo-terminal-allocation/m-p/5277539#M474010</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2011-03-24T15:54:56Z</dc:date>
    </item>
  </channel>
</rss>

