KVC@engvax.UUCP (Kevin Carosso) (09/16/87)
> 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