Re: timeout an inactive login session

From: Randy Styka (randy_at_computron.com)
Date: 11/16/03

  • Next message: Eric de Redelijkheid: "Re: Tru64 to HP-UX 11i v2 survey question suggestions requested for Tru64.org survey"
    Date: Sun, 16 Nov 2003 05:40:13 GMT
    
    

    taz wrote:
    > We are setting up enhanced security on a V4.0f system. One of the corporate
    > requirements is that any login session that has been idle for XX amount of
    > time needs to be automatically logged out. I have not been able to find
    > this capability in the documentation, but I have to believe that it is
    > there. How do we enforce this for ALL logins?

    With most shells, there is a variable that can be set that may help.
    In ksh, for instance, the variable TMOUT sets the number of minutes you
    can be idle before being logged off. It varies by shell.

    Note, however, that this ONLY works for users at a shell prompt, not in
    applications.

    If you want a general way of enforcing this for all interactive
    sessions, we wrote/sell a product called LOGMON. It is available
    for Tru64 as well as a lot of other Unix variants.

    This software monitors the cpu usage of each user, and their child
    processes, to make sure the user really is idle. This is important,
    as commands like "who -u" show you an idle time based on keyboard
    activity only. If you run a long cpu bound job, "who -u" will show you
    as idle, even while the job is running. But since we monitor cpu usage
    also, you would not be logged off.

    You can vary the inactivity time by user, time of day, etc. You can
    control how the user is logged off.

    For details, send a message to logmon@computron.com or visit
    www.logmon.com Thanks!

    Randy Styka, randy@computron.com, 630/941-7767


  • Next message: Eric de Redelijkheid: "Re: Tru64 to HP-UX 11i v2 survey question suggestions requested for Tru64.org survey"

    Relevant Pages

    • Re: Re: Complete frustration
      ... I want to edit it then I'll choose the "Edit with IDLE" context menu. ... But changing the PATH environment variable affects a command typed in the shell, but does not affect what happens when you either type the name of a python script directly, or when you double-click on such a file. ...
      (comp.lang.python)
    • Re: CPU Running at 100%
      ... I understand that Idle + CPU Usage should be 100%. ... >> I installed Process Explorer and it shows that almost all of the time ... >> spent in Hardware interrupts, which may be due to the virus scan. ...
      (microsoft.public.windowsxp.perform_maintain)
    • a curious IDLE Error
      ... Windows 2000, Python 2.3, using IDLE file editor and shell ... I closed the IDLE shell, re-ran the module, which opened a new IDLE shell ... I opened a separate instance of Python and tried the raw_input ...
      (comp.lang.python)
    • Re: Why my modification of source file doesnt take effect whendebugging?
      ... Idle was dropped. ... I'm sure I'm not the only one who lost lots of time because of that bug. ... Sane people will assume that when you edit file1.py and press F5, it reparses the file, but when you edit file2.py and press F5 with file1.py it won't work. ... Why make is so that I have to select the shell window, press CTRL+F6, select the file1.py and press F5 just so that it works as expected? ...
      (comp.lang.python)
    • Re: timeout an inactive login session
      ... Idle means no keyboard/mouse activity. ... Login session would be the minimum. ... Can this be done with V4.0F and Enhanced security?? ... >> corporate requirements is that any login session that has been idle ...
      (comp.unix.tru64)