Re: cut off after 30-45 minutes inactivity

[Jeff.Ogden]

FYI
---(Forwarded from: norman_manny@emunix.emich.edu, Dated: Fri, 21 Aug 92 10:19:24 EDT)---
Received: from merit.edu by um.cc.umich.edu via Internet with TCP; Fri, 21 Aug 92 10:34:15 EDT
Return-Path: <norman_manny@emunix.emich.edu>
Received: from emunix.emich.edu by merit.edu (5.65/1123-1.0)
        id AA21004; Fri, 21 Aug 92 10:23:24 -0400
Received: from EMU_ACADEMIC:.Nodes.red.DECnet MAIL11D_V3 by emunix.emich.edu (5.57/Ultrix3.0-C)
        id AA12417; Fri, 21 Aug 92 10:19:26 -0400
Date: Fri, 21 Aug 92 10:19:25 -0400
Message-Id: <9208211419.AA12417@emunix.emich.edu>
From: norman_manny@emunix.emich.edu (Manny Norman, Sr. Systems Programmer, Learning Technologies)
To: emunix::"MOORERR@msu.edu"@merit.edu
Cc: emunix::"mjts@merit.edu"@merit.edu
Subject: Re: cut off after 30-45 minutes inactivity
 
        We have an inactivity cut-off time of 10 minutes on our VAX cluster.
This is because users would walk away from the terminals without logging out 
and other (sick?) users would then do damage to the logged-on accounts.
 
        I would consider 8 hours of inactivity holding on to a line as grossly 
inconsiderate.  I think the idea of a relatively short time, the suggested 30 
to 45 minutes of inactivity OK for cutting off, together with a limit of quite 
a few hours of connect time.  Users should be warned as the cutoff time 
approches.
 
        Manny.
- - - - - - - - - - - - - - - - -