<?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: HP-UX hanging telnet session in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402483#M201080</link>
    <description>The TMOUT variable in configuration prior to the script may help.&lt;BR /&gt;&lt;BR /&gt;It does help if the user is just sitting on the command prompt.&lt;BR /&gt;&lt;BR /&gt;insf -e might help if the problem is being generated by bad pseudo device drivers.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Mon, 18 Oct 2004 16:15:02 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2004-10-18T16:15:02Z</dc:date>
    <item>
      <title>HP-UX hanging telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402481#M201078</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;There any way to identify the hanging telnet sessions ?&lt;BR /&gt;&lt;BR /&gt;If the user logs into the machine through telnet and closes the window without exiting properly , whether those sessions cleaned up after a specific time ?? What is the time period for that ?&lt;BR /&gt;&lt;BR /&gt;We need this info because the user will be running some interactive scripts in those telnet sessions and if the user does not exit properly, we need to clean up those scripts (which will be child process of that telnet session).&lt;BR /&gt;&lt;BR /&gt;Please let us know if u have any suggestions.&lt;BR /&gt;&lt;BR /&gt;Arun</description>
      <pubDate>Mon, 18 Oct 2004 10:33:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402481#M201078</guid>
      <dc:creator>hptcsdev</dc:creator>
      <dc:date>2004-10-18T10:33:32Z</dc:date>
    </item>
    <item>
      <title>Re: HP-UX hanging telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402482#M201079</link>
      <description>&lt;BR /&gt;You could write a script to look for the scripts that don't have tty's associated with them, then blow them away.&lt;BR /&gt;&lt;BR /&gt;I haven't seen that behavior with telnet. Are your scripts doing trap's?&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Mon, 18 Oct 2004 14:48:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402482#M201079</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2004-10-18T14:48:11Z</dc:date>
    </item>
    <item>
      <title>Re: HP-UX hanging telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402483#M201080</link>
      <description>The TMOUT variable in configuration prior to the script may help.&lt;BR /&gt;&lt;BR /&gt;It does help if the user is just sitting on the command prompt.&lt;BR /&gt;&lt;BR /&gt;insf -e might help if the problem is being generated by bad pseudo device drivers.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 18 Oct 2004 16:15:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402483#M201080</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-10-18T16:15:02Z</dc:date>
    </item>
    <item>
      <title>Re: HP-UX hanging telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402484#M201081</link>
      <description>Hi Arun,&lt;BR /&gt;&lt;BR /&gt;If the telnet session exits, then all the child processes that were spawned by it should also die unless they were started with 'nohup' option. &lt;BR /&gt;&lt;BR /&gt;You can probably modify the script to output the pids of the subshells into a file in some directory including it's own. Have a cronjob that checks those files periodically. If the pid of the script is not found in the 'ps -ef' list, then it can go ahead and kill rest of the pids in that file. Not a 100% sure shot, but it can be the closest you have.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Mon, 18 Oct 2004 16:26:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402484#M201081</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2004-10-18T16:26:08Z</dc:date>
    </item>
    <item>
      <title>Re: HP-UX hanging telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402485#M201082</link>
      <description>This problem usually happens when the PC is shut off.  The sessions will not time out unless your telnetd supports keepalive.&lt;BR /&gt;&lt;BR /&gt;It's possible to write a script that kills idle sessions, but I hate those.&lt;BR /&gt;&lt;BR /&gt;My suggestion: Move off telnet and switch to ssh.  There are good client programs like putty that can be used to talk over ssh.  This will give you keepalives (you may need to configure the server to turn them on).&lt;BR /&gt;</description>
      <pubDate>Mon, 18 Oct 2004 16:47:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402485#M201082</guid>
      <dc:creator>Ron Kuris</dc:creator>
      <dc:date>2004-10-18T16:47:08Z</dc:date>
    </item>
    <item>
      <title>Re: HP-UX hanging telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402486#M201083</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The tty for handing sessions is still "pts/tj". This remains the same even after hours.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;We hav a daemon scheduled, which kills all our script running with (tty=? or ppid=1) But this is not working now as the tty remains the same and not changing to '?' even after the parent session is closed.&lt;BR /&gt;&lt;BR /&gt;What could be the problem here ??&lt;BR /&gt;&lt;BR /&gt;Also I have no idea how to check if the 'telnetd' supports 'keepalive'. Could anyone help me out on this..And how to change the behaviour to automatically terminate the hanging telnet sessions ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Arun</description>
      <pubDate>Tue, 19 Oct 2004 00:54:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402486#M201083</guid>
      <dc:creator>hptcsdev</dc:creator>
      <dc:date>2004-10-19T00:54:28Z</dc:date>
    </item>
    <item>
      <title>Re: HP-UX hanging telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402487#M201084</link>
      <description>Hi Arun&lt;BR /&gt;Use netstat -a|grep FIN to find the lost telnet connections.&lt;BR /&gt;&lt;BR /&gt;use this script sweep&lt;BR /&gt;&lt;BR /&gt;#!/usr/bin/ksh&lt;BR /&gt;#&lt;BR /&gt;# "flush_stale_finw2" -- Wolffman 6/2/98&lt;BR /&gt;#&lt;BR /&gt;# Script to flush stale FIN_WAIT_2 sockets.&lt;BR /&gt;# Script execution with the "-f" option results in&lt;BR /&gt;# HP machine sending TCP RST along with clean release&lt;BR /&gt;# and freeing of associated connection resources.&lt;BR /&gt;# (Essentially, returning kernel memory back for reuse.)&lt;BR /&gt;#&lt;BR /&gt;# Suggestion: invoke via "cron" job during off hours&lt;BR /&gt;#&lt;BR /&gt;#&lt;BR /&gt;#&lt;BR /&gt;# Usage: flush_stale_finw2 # To list sockets in FIN_WAIT_2 state&lt;BR /&gt;# flush_stale_finw2 -f # To actually force their removal&lt;BR /&gt;#&lt;BR /&gt;#&lt;BR /&gt;if test "$1" = "-f"&lt;BR /&gt;then&lt;BR /&gt;/usr/bin/ndd -get /dev/tcp tcp_status | grep FIN_WAIT_2 |&lt;BR /&gt;awk '{ printf "ndd -set /dev/tcp tcp_discon 0x%s\n", $1 }' &amp;gt; /tmp/finw2&lt;BR /&gt;/sbin/chmod 700 /tmp/finw2&lt;BR /&gt;/usr/bin/ksh -x /tmp/finw2&lt;BR /&gt;&lt;BR /&gt;/sbin/rm /tmp/finw2&lt;BR /&gt;else&lt;BR /&gt;/usr/bin/ndd -get /dev/tcp tcp_status | grep FIN_WAIT_2&lt;BR /&gt;fi&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Infact the same was alreadydisccused in a previuos thread&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;SK</description>
      <pubDate>Tue, 19 Oct 2004 02:53:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402487#M201084</guid>
      <dc:creator>Sยภเl Kย๓คг</dc:creator>
      <dc:date>2004-10-19T02:53:46Z</dc:date>
    </item>
    <item>
      <title>Re: HP-UX hanging telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402488#M201085</link>
      <description>&lt;BR /&gt;WHat version of HPux are you running?&lt;BR /&gt;&lt;BR /&gt;When was the last set of network patches applied?&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Tue, 19 Oct 2004 06:59:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-hanging-telnet-session/m-p/3402488#M201085</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2004-10-19T06:59:04Z</dc:date>
    </item>
  </channel>
</rss>

