<?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: Timeout inactive telnet session in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/timeout-inactive-telnet-session/m-p/3560359#M18064</link>
    <description>TMOUT was never designed to work once an application was invoked.&lt;BR /&gt;&lt;BR /&gt;Its up to the application developer/administrator to configure the application to time out the user. Then TMOUT will work.&lt;BR /&gt;&lt;BR /&gt;This behavior is by design. Imagine what would happen if TMOUT killed a session while it was say updating some oracle data without keyboard input.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Wed, 08 Jun 2005 10:25:43 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2005-06-08T10:25:43Z</dc:date>
    <item>
      <title>Timeout inactive telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-linux/timeout-inactive-telnet-session/m-p/3560358#M18063</link>
      <description>I found that I could timeout inactive telnet session by setting TMOUT environment variable:&lt;BR /&gt;&lt;BR /&gt;# export TMOUT=10&lt;BR /&gt;&lt;BR /&gt;then if I stay in shell, I will be kicked out after 10 seconds:&lt;BR /&gt;&lt;BR /&gt;# timed out waiting for input: auto-logout&lt;BR /&gt;Connection to host lost.&lt;BR /&gt;&lt;BR /&gt;But if I run some applications after login to the shell, the Timeout didn't work. For example, I did a test to run "top" after setting TMOUT=10, but the telnet seesion didn't timeout until I quited "top" back to the shell, and counted another 10 seconds... &lt;BR /&gt;&lt;BR /&gt;Now I need to kick out inactive users who run an Oracle application after they login to the shell, force them logout after they finish their shift.&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Wed, 08 Jun 2005 10:12:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/timeout-inactive-telnet-session/m-p/3560358#M18063</guid>
      <dc:creator>yyghp</dc:creator>
      <dc:date>2005-06-08T10:12:01Z</dc:date>
    </item>
    <item>
      <title>Re: Timeout inactive telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-linux/timeout-inactive-telnet-session/m-p/3560359#M18064</link>
      <description>TMOUT was never designed to work once an application was invoked.&lt;BR /&gt;&lt;BR /&gt;Its up to the application developer/administrator to configure the application to time out the user. Then TMOUT will work.&lt;BR /&gt;&lt;BR /&gt;This behavior is by design. Imagine what would happen if TMOUT killed a session while it was say updating some oracle data without keyboard input.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 08 Jun 2005 10:25:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/timeout-inactive-telnet-session/m-p/3560359#M18064</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-06-08T10:25:43Z</dc:date>
    </item>
    <item>
      <title>Re: Timeout inactive telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-linux/timeout-inactive-telnet-session/m-p/3560360#M18065</link>
      <description>The system is acting the way it is supposed to be. If you just start something and live it that way, the shell will not timeout.&lt;BR /&gt;&lt;BR /&gt;You may need to look at idle time (from who -uH) and explicitly kill such sessions. You need to be very careful when doing this. Educating the users will also help you a lot.&lt;BR /&gt;&lt;BR /&gt;Anil</description>
      <pubDate>Wed, 08 Jun 2005 10:27:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/timeout-inactive-telnet-session/m-p/3560360#M18065</guid>
      <dc:creator>RAC_1</dc:creator>
      <dc:date>2005-06-08T10:27:00Z</dc:date>
    </item>
    <item>
      <title>Re: Timeout inactive telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-linux/timeout-inactive-telnet-session/m-p/3560361#M18066</link>
      <description>Thanks Steven and RAC !&lt;BR /&gt;Yes, it's reasonable that the TMOUT is acting like this. &lt;BR /&gt;But I noticed some users didn't logout their sessions on their devices after their shift, by checking the idle time ( who -u ), is there any better solution for this besides educating them ?&lt;BR /&gt;</description>
      <pubDate>Wed, 08 Jun 2005 10:53:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/timeout-inactive-telnet-session/m-p/3560361#M18066</guid>
      <dc:creator>yyghp</dc:creator>
      <dc:date>2005-06-08T10:53:57Z</dc:date>
    </item>
    <item>
      <title>Re: Timeout inactive telnet session</title>
      <link>https://community.hpe.com/t5/operating-system-linux/timeout-inactive-telnet-session/m-p/3560362#M18067</link>
      <description>There used to be a daemon called 'idled', of which would log-out terminals idle for a given period of time.  But this package is no longer maintained.&lt;BR /&gt;&lt;BR /&gt;There is also one called 'timeoutd', but i've never used it and can't access the source tree any more.&lt;BR /&gt;&lt;BR /&gt;What appears to be more recent is the 'autolog' program.  I can't find any RH packages, but you should be able to grab the SuSE src.rpm and rebuild it for your platform.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="ftp://ftp.suse.com/pub/suse/i386/9.3/suse/src/autolog-0.35-722.src.rpm" target="_blank"&gt;ftp://ftp.suse.com/pub/suse/i386/9.3/suse/src/autolog-0.35-722.src.rpm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;for example.</description>
      <pubDate>Wed, 08 Jun 2005 18:43:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/timeout-inactive-telnet-session/m-p/3560362#M18067</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2005-06-08T18:43:53Z</dc:date>
    </item>
  </channel>
</rss>

