<?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: remsh timeout in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/remsh-timeout/m-p/2780308#M832532</link>
    <description>You could attempt changing the tcp wait state..&lt;BR /&gt;&lt;BR /&gt;#ndd -get /dev/tcp tcp_time_wait_interval&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;will show the default setting, typically 60000 (60s) to change use&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;#ndd -set /dev/tcp tcp_time_wait_interval 30000&lt;BR /&gt;&lt;BR /&gt;for example..&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
    <pubDate>Tue, 06 Aug 2002 07:20:47 GMT</pubDate>
    <dc:creator>Bill McNAMARA_1</dc:creator>
    <dc:date>2002-08-06T07:20:47Z</dc:date>
    <item>
      <title>remsh timeout</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/remsh-timeout/m-p/2780307#M832531</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Is it possible to configure the timeout of the remsh command ?&lt;BR /&gt;&lt;BR /&gt;Regards.</description>
      <pubDate>Tue, 06 Aug 2002 07:09:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/remsh-timeout/m-p/2780307#M832531</guid>
      <dc:creator>Hamerlik Christophe</dc:creator>
      <dc:date>2002-08-06T07:09:09Z</dc:date>
    </item>
    <item>
      <title>Re: remsh timeout</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/remsh-timeout/m-p/2780308#M832532</link>
      <description>You could attempt changing the tcp wait state..&lt;BR /&gt;&lt;BR /&gt;#ndd -get /dev/tcp tcp_time_wait_interval&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;will show the default setting, typically 60000 (60s) to change use&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;#ndd -set /dev/tcp tcp_time_wait_interval 30000&lt;BR /&gt;&lt;BR /&gt;for example..&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Tue, 06 Aug 2002 07:20:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/remsh-timeout/m-p/2780308#M832532</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2002-08-06T07:20:47Z</dc:date>
    </item>
    <item>
      <title>Re: remsh timeout</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/remsh-timeout/m-p/2780309#M832533</link>
      <description>If you are trying to cut down on time to run a command in the event of a host not being there you could try a ping host -n 1 and check the result of this before issuing the remsh.</description>
      <pubDate>Tue, 06 Aug 2002 07:25:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/remsh-timeout/m-p/2780309#M832533</guid>
      <dc:creator>Pierce Byrne_1</dc:creator>
      <dc:date>2002-08-06T07:25:30Z</dc:date>
    </item>
    <item>
      <title>Re: remsh timeout</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/remsh-timeout/m-p/2780310#M832534</link>
      <description>Thanks,&lt;BR /&gt;&lt;BR /&gt;I have just changed the tcp time_wait... but it doesn't look to change something.&lt;BR /&gt;&lt;BR /&gt;I have already thought of the solution with ping. But I need to know very fast if the host is up or down on the network and so the timeout of "ping host -n 1" is too long for my needs.&lt;BR /&gt;&lt;BR /&gt;Regards.</description>
      <pubDate>Tue, 06 Aug 2002 07:31:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/remsh-timeout/m-p/2780310#M832534</guid>
      <dc:creator>Hamerlik Christophe</dc:creator>
      <dc:date>2002-08-06T07:31:20Z</dc:date>
    </item>
    <item>
      <title>Re: remsh timeout</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/remsh-timeout/m-p/2780311#M832535</link>
      <description>check via netstat -an | grep ip the ports states.. when you figure out what state the port is in, you can then use ndd to tune better.&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Tue, 06 Aug 2002 09:08:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/remsh-timeout/m-p/2780311#M832535</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2002-08-06T09:08:43Z</dc:date>
    </item>
  </channel>
</rss>

