.ps 58,70
.ap
.p 0
.c;==============================================
.c;SECURITY --- Idle Process Killer         V2.0
.c;==============================================
.s
.c;by
.s
.c;G. Beau Williamson
.c;Rockwell International
.c;1200 N. Alma Rd.
.c;Richardson, TX. 75081
.c;(214) 996-5547
.s1
.c;Updated by: George Flint
.c;23-June-1988
.s2
.c;ABSTRACT
.c;--------
The Security program is an idle terminal watch program that monitors the system
for terminals that have been left idle and automatically logs them off if
it has been idle a specified period of time.  A terminal (process) is
considered idle by Security if it has not generated a minimum amount of
CPU time or a minimum number of Buffered IO's during a set time period.

.note
The name "SECURITY" was chosen as it had a nice official ring to it when the
user was notified with the message, "You have been logged out by SECURITY". 
.end note

Security also has a "Critical Image" feature that permits interactive processes
that are executing certain critical images to become immune from Security's
auto-logout functions.  An example of a typical critical image is the "RTPAD"
image which is executed when a "SET HOST" command is issued.  By designating
"RTPAD" as a critical image, Security will not logoff a local process that
appears to be idle that is in fact executing a compute-bound job on the remote
host. 

The following is a summary of the basic features of Security V2.0.

.list
.le;Idle terminals are logged out when idle period is exceeded.
.le;Idle terminals may, optionally be warned of pending logout.
.le;Security Alarms are optionally sent to OPCOM when a terminal is logged out.
.le;Subprocess activity is included in the idle computations.
.le;Processes running "Critical Images" are immune.
.le;The list of "Critical Images" may be modified.                         
.le;A Log file of all Security activity is produced.
.le;All Operational Parameters may be set via system logicals.
.els