<?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 - idle session timeout in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487708#M38085</link>
    <description>Hi Matti Kurkela  &lt;BR /&gt;&lt;BR /&gt;&amp;gt;These settings have no effect if the network connection is OK and the user is &lt;BR /&gt;&amp;gt;just idle (or has walked away from his/her keyboard).&lt;BR /&gt;Thanks for explaining. But how do you find this explanation ;) ? .&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Note that this timeout works only if the user has become idle when the &lt;BR /&gt;&amp;gt;session is at the shell prompt: if the user has started a program and then &lt;BR /&gt;&amp;gt;walked away, the idleness detection must happen within that program &lt;BR /&gt;&lt;BR /&gt;then whats the solution ?&lt;BR /&gt;actually we need to lock and/or disconnect the idle users.&lt;BR /&gt;we normally logs on the server via ssh, but some users also logs on via vnc.&lt;BR /&gt;&lt;BR /&gt;so if a user run vi(or any other program) and left his/her seat, then TMOUT is not a solution.&lt;BR /&gt;&lt;BR /&gt;so is there any good solution ?&lt;BR /&gt;&lt;BR /&gt;Hi Ivan Ferreira&lt;BR /&gt;&amp;gt;For your case, probably you need to write an script to kill a process that is &lt;BR /&gt;&amp;gt;IDLE for the required time. &lt;BR /&gt;you mean script will first kill the processes belongs to the idle user, and &lt;BR /&gt;then TMOUT will automatically logout the user ? because I just dont want to &lt;BR /&gt;kill idle user processes, but also disconnect those users too.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;There are some scripts for doing this arround.&lt;BR /&gt;please share ;)&lt;BR /&gt;&lt;BR /&gt;Hi Steven E. Protter, thanks for the help&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Maaz</description>
    <pubDate>Mon, 31 Aug 2009 05:35:26 GMT</pubDate>
    <dc:creator>Maaz</dc:creator>
    <dc:date>2009-08-31T05:35:26Z</dc:date>
    <item>
      <title>ssh - idle session timeout</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487704#M38081</link>
      <description>openssh-4.2p1-18.38.3&lt;BR /&gt;SLES 10 SP2&lt;BR /&gt;# uname -r&lt;BR /&gt;2.6.16.60-0.21-smp&lt;BR /&gt;&lt;BR /&gt;I want to disconnect those ssh clients, who are idle more then 14 mintues&lt;BR /&gt;&lt;BR /&gt;On ssh server, in /etc/ssh/sshd_config&lt;BR /&gt;&lt;BR /&gt;ClientAliveInterval 5&lt;BR /&gt;ClientAliveCountMax 3&lt;BR /&gt;&lt;BR /&gt;then restart the ssh daemon.&lt;BR /&gt;&lt;BR /&gt;from ssh client(another SLE 10 SP2 box), I logs on the server, and did nothing(idle) for 20 minutes, but session was valid/remain.&lt;BR /&gt;&lt;BR /&gt;what I am missing, please help&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Maaz&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 28 Aug 2009 06:03:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487704#M38081</guid>
      <dc:creator>Maaz</dc:creator>
      <dc:date>2009-08-28T06:03:12Z</dc:date>
    </item>
    <item>
      <title>Re: ssh - idle session timeout</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487705#M38082</link>
      <description>Your ClientAliveInterval and ClientAliveCountMax settings would terminate the connection in 15 seconds if your user pulls the plug (network or power) on his/her workstation without first logging out from the server. &lt;BR /&gt;&lt;BR /&gt;These settings have no effect if the network connection is OK and the user is just idle (or has walked away from his/her keyboard).&lt;BR /&gt;&lt;BR /&gt;I assume you use the default "bash" as the standard shell for your users?&lt;BR /&gt;In that case, add this to your /etc/profile:&lt;BR /&gt;&lt;BR /&gt;export TMOUT=840 # 14 minutes in seconds&lt;BR /&gt;typeset -r TMOUT&lt;BR /&gt;&lt;BR /&gt;The second command makes the TMOUT variable read-only, so the users cannot disable the timeout.&lt;BR /&gt;&lt;BR /&gt;Note that this timeout works only if the user has become idle when the session is at the shell prompt: if the user has started a program and then walked away, the idleness detection must happen within that program (because the OS and the shell won't know whether a program can be stopped without causing data loss).&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Fri, 28 Aug 2009 07:12:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487705#M38082</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-08-28T07:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: ssh - idle session timeout</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487706#M38083</link>
      <description>For your case, probably you need to write an script to kill a process that is IDLE for the required time. Check the ouput of the "w" command to get the IDLE status and time. There are some scripts for doing this arround.</description>
      <pubDate>Fri, 28 Aug 2009 11:57:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487706#M38083</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2009-08-28T11:57:00Z</dc:date>
    </item>
    <item>
      <title>Re: ssh - idle session timeout</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487707#M38084</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;This change will not help.&lt;BR /&gt;&lt;BR /&gt;TMEOUT variable in the shell will help with idle ssh sessions.&lt;BR /&gt;&lt;BR /&gt;Once an application, even vi is run, TMEOUT will not help.&lt;BR /&gt;&lt;BR /&gt;It is TIMEOUT in some distributions.&lt;BR /&gt;&lt;BR /&gt;SEP&lt;BR /&gt;hpuxconsulting in yahoo messenger.</description>
      <pubDate>Sun, 30 Aug 2009 13:00:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487707#M38084</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-08-30T13:00:12Z</dc:date>
    </item>
    <item>
      <title>Re: ssh - idle session timeout</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487708#M38085</link>
      <description>Hi Matti Kurkela  &lt;BR /&gt;&lt;BR /&gt;&amp;gt;These settings have no effect if the network connection is OK and the user is &lt;BR /&gt;&amp;gt;just idle (or has walked away from his/her keyboard).&lt;BR /&gt;Thanks for explaining. But how do you find this explanation ;) ? .&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Note that this timeout works only if the user has become idle when the &lt;BR /&gt;&amp;gt;session is at the shell prompt: if the user has started a program and then &lt;BR /&gt;&amp;gt;walked away, the idleness detection must happen within that program &lt;BR /&gt;&lt;BR /&gt;then whats the solution ?&lt;BR /&gt;actually we need to lock and/or disconnect the idle users.&lt;BR /&gt;we normally logs on the server via ssh, but some users also logs on via vnc.&lt;BR /&gt;&lt;BR /&gt;so if a user run vi(or any other program) and left his/her seat, then TMOUT is not a solution.&lt;BR /&gt;&lt;BR /&gt;so is there any good solution ?&lt;BR /&gt;&lt;BR /&gt;Hi Ivan Ferreira&lt;BR /&gt;&amp;gt;For your case, probably you need to write an script to kill a process that is &lt;BR /&gt;&amp;gt;IDLE for the required time. &lt;BR /&gt;you mean script will first kill the processes belongs to the idle user, and &lt;BR /&gt;then TMOUT will automatically logout the user ? because I just dont want to &lt;BR /&gt;kill idle user processes, but also disconnect those users too.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;There are some scripts for doing this arround.&lt;BR /&gt;please share ;)&lt;BR /&gt;&lt;BR /&gt;Hi Steven E. Protter, thanks for the help&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Maaz</description>
      <pubDate>Mon, 31 Aug 2009 05:35:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487708#M38085</guid>
      <dc:creator>Maaz</dc:creator>
      <dc:date>2009-08-31T05:35:26Z</dc:date>
    </item>
    <item>
      <title>Re: ssh - idle session timeout</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487709#M38086</link>
      <description>&amp;gt;&amp;gt;want to disconnect those ssh clients, who are idle more then 14 mintues&lt;BR /&gt;&lt;BR /&gt;here is the solution ... following works ;-)&lt;BR /&gt;&lt;BR /&gt;ClientAliveInterval 900&lt;BR /&gt;ClientAliveCountMax 0&lt;BR /&gt;&lt;BR /&gt;Matti Kurkela&lt;BR /&gt;&amp;gt;These settings have no effect if the network&lt;BR /&gt;&amp;gt;connection is OK and the user is just idle &amp;gt;or&lt;BR /&gt;&amp;gt;has walked away from his/her keyboard).&lt;BR /&gt;Dear, the above setting will disconnect the idle session of the user... even if the network connection is OK&lt;BR /&gt;&lt;BR /&gt;thanks for help&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Maaz</description>
      <pubDate>Mon, 14 Sep 2009 04:50:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-idle-session-timeout/m-p/4487709#M38086</guid>
      <dc:creator>Maaz</dc:creator>
      <dc:date>2009-09-14T04:50:53Z</dc:date>
    </item>
  </channel>
</rss>

