Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!cmcl2!rutgers!ucla-cs!zen!ucbvax!engvax.UUCP!KVC
From: KVC@engvax.UUCP (Kevin Carosso)
Newsgroups: comp.os.vms
Subject: Idle job killers
Message-ID: <8709160222.AA26403@csvax.caltech.edu>
Date: Tue, 15-Sep-87 22:18:19 EDT
Article-I.D.: csvax.8709160222.AA26403
Posted: Tue Sep 15 22:18:19 1987
Date-Received: Sat, 19-Sep-87 12:11:38 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20

> BTW, Why write another Idle Job Killer? (Why climb a mountain?)
> Because it is a crazy thing to do. This Job Killer only kills interactive jobs
> where all subprocesses are inactive.

I was just getting set to send out the idle job killer we use.  I detailed
it to INFO-VAX last month sometime with a promise to send it once I was satisfied
that it was solid.  In case you're new to the list, it has the following
features:

	o Considers an entire job "tree" for idleness, not just
	  per process.  Hence leaves your idle editor subprocess
	  alone while you are doing other things.
	o Considers only interactive processes on terminals for idleness.
	o Disconnects you rather than logs you out whenever possible.
	o User utility to set what they consider to be their own "idle" time,
	  within limits defined by the SYSMGR.
	o Has a config file so the system manager can tailor these things.

	/Kevin Carosso                     kvc@engvax.scg.hac.com
	 Hughes Aircraft Co.               kvc%engvax@oberon.usc.edu