<?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 User idle time in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/user-idle-time/m-p/2427874#M1975</link>
    <description>How can I kick out users that are over an hour idle.  A lot of my users don't log out at all.  I know I can kick them out individually but wanted to know if there is some kind of setting out there that I am unaware of.&lt;BR /&gt;</description>
    <pubDate>Tue, 27 Jun 2000 17:34:00 GMT</pubDate>
    <dc:creator>Unix Administrator_6</dc:creator>
    <dc:date>2000-06-27T17:34:00Z</dc:date>
    <item>
      <title>User idle time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/user-idle-time/m-p/2427874#M1975</link>
      <description>How can I kick out users that are over an hour idle.  A lot of my users don't log out at all.  I know I can kick them out individually but wanted to know if there is some kind of setting out there that I am unaware of.&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Jun 2000 17:34:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/user-idle-time/m-p/2427874#M1975</guid>
      <dc:creator>Unix Administrator_6</dc:creator>
      <dc:date>2000-06-27T17:34:00Z</dc:date>
    </item>
    <item>
      <title>Re: User idle time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/user-idle-time/m-p/2427875#M1976</link>
      <description>I don't know of any automated command to do this, but here are some thoughts...  There is an inherent danger with logging people out of a machine.  Who knows what type of processing they are/have been performing.  For example, they could be in some data entry screen within a RDBMS where the execution point there sitting on may not have written to all the required files.  One hour idle time may seem long but I think it's a bit short when you consider the potential ramifications.  A better method may be to log off inactive user processes when you perform your daily backups.  The preferred method would be to use kill -1 (SIGHUP).  My strong suggestion would be to discuss the issue with your DBA's and application developers before you set anything in stone.  It's a good chance that they are the worst culprits to which the best solution is to relegate them to a separate test machine.</description>
      <pubDate>Tue, 27 Jun 2000 18:01:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/user-idle-time/m-p/2427875#M1976</guid>
      <dc:creator>Tim Malnati</dc:creator>
      <dc:date>2000-06-27T18:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: User idle time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/user-idle-time/m-p/2427876#M1977</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;For telnet sessoins you can try setting "TMOUT" shell variable in .profile to some number of seconds. Idle sessions will get dropped after specified period. Works for sure with ksh.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;TT</description>
      <pubDate>Tue, 27 Jun 2000 18:20:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/user-idle-time/m-p/2427876#M1977</guid>
      <dc:creator>Thomas G. Tudrej</dc:creator>
      <dc:date>2000-06-27T18:20:07Z</dc:date>
    </item>
    <item>
      <title>Re: User idle time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/user-idle-time/m-p/2427877#M1978</link>
      <description>Both good answers.  If you simply must find users to boot on the basis of idle time, then you can parse the value out of w (or uptime).  This works for any users that connect through a standard login shell, but it will not find users that hit the box through an applications socket which does not spawn a shell session.&lt;BR /&gt;&lt;BR /&gt;One note: make sure to select processes to kill based upon tty, not userid, since a user may have multiple logins open.</description>
      <pubDate>Tue, 27 Jun 2000 19:12:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/user-idle-time/m-p/2427877#M1978</guid>
      <dc:creator>Alan Riggs</dc:creator>
      <dc:date>2000-06-27T19:12:01Z</dc:date>
    </item>
  </channel>
</rss>

