<?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: login session timeout in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/login-session-timeout/m-p/2536788#M26085</link>
    <description>And for csh users, the variable is autologout and the units are in minutes.  To force users to adhere to the TMOUT value (ksh, POSIX, bash) you can put this statement into /etc/profile:&lt;BR /&gt;&lt;BR /&gt;export readonly TMOUT=14400&lt;BR /&gt;&lt;BR /&gt;which forces every login shell to timeout in 4 hours or no activity.  Note this also affects root's login and once set to readonly, the value in the shell cannot be changed, even by root. It's often common to set root's timeout to less than an hour to avoid open sessions on an open terminal or console.&lt;BR /&gt;&lt;BR /&gt;Note that this timeout only counts time when the shell is idle.  If a smart user starts another shell or perhaps a copy of vi, the timer will not run and the 'session' will never timeout.</description>
    <pubDate>Wed, 06 Jun 2001 01:35:49 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2001-06-06T01:35:49Z</dc:date>
    <item>
      <title>login session timeout</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/login-session-timeout/m-p/2536786#M26083</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;can anyone tell me how to set up inactivity  time out for user sessions in HP-UX 11.0?&lt;BR /&gt;&lt;BR /&gt;Thanks &amp;amp; regards,&lt;BR /&gt;Jegi&lt;BR /&gt;NBC</description>
      <pubDate>Tue, 05 Jun 2001 19:30:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/login-session-timeout/m-p/2536786#M26083</guid>
      <dc:creator>Jeganathan Venkitasamy</dc:creator>
      <dc:date>2001-06-05T19:30:41Z</dc:date>
    </item>
    <item>
      <title>Re: login session timeout</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/login-session-timeout/m-p/2536787#M26084</link>
      <description>There's no general purpose mechanism I know of that works in all situations, but putting&lt;BR /&gt;  TMOUT=seconds; export TMOUT&lt;BR /&gt;in /etc/profile will set the shell-level timeout for all users of sh or ksh to &lt;SECONDS&gt;.  1800 would be a typical value.&lt;/SECONDS&gt;</description>
      <pubDate>Tue, 05 Jun 2001 19:49:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/login-session-timeout/m-p/2536787#M26084</guid>
      <dc:creator>Chris Calabrese</dc:creator>
      <dc:date>2001-06-05T19:49:44Z</dc:date>
    </item>
    <item>
      <title>Re: login session timeout</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/login-session-timeout/m-p/2536788#M26085</link>
      <description>And for csh users, the variable is autologout and the units are in minutes.  To force users to adhere to the TMOUT value (ksh, POSIX, bash) you can put this statement into /etc/profile:&lt;BR /&gt;&lt;BR /&gt;export readonly TMOUT=14400&lt;BR /&gt;&lt;BR /&gt;which forces every login shell to timeout in 4 hours or no activity.  Note this also affects root's login and once set to readonly, the value in the shell cannot be changed, even by root. It's often common to set root's timeout to less than an hour to avoid open sessions on an open terminal or console.&lt;BR /&gt;&lt;BR /&gt;Note that this timeout only counts time when the shell is idle.  If a smart user starts another shell or perhaps a copy of vi, the timer will not run and the 'session' will never timeout.</description>
      <pubDate>Wed, 06 Jun 2001 01:35:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/login-session-timeout/m-p/2536788#M26085</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2001-06-06T01:35:49Z</dc:date>
    </item>
  </channel>
</rss>

