Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!columbia!rutgers!ucla-cs!zen!ucbvax!eg.ti.COM!THURY%MCOPN1 From: THURY%MCOPN1@eg.ti.COM (Denny Thury -- VAX System Sup -- 952-2066) Newsgroups: comp.os.vms Subject: RE: time out idle users Message-ID: <8707250327.AA03135@ucbvax.Berkeley.EDU> Date: Fri, 24-Jul-87 18:33:00 EDT Article-I.D.: ucbvax.8707250327.AA03135 Posted: Fri Jul 24 18:33:00 1987 Date-Received: Sat, 25-Jul-87 17:12:06 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 26 In an earlier message, Kevin Carosso discussed an idle process monitor, by Chris Yoder, that would disconnect, instead of delete, an inactive process. During that discussion, Kevin mentioned something called CLASS_DISCONNECT. Sorry to bother the entire net with this, but CSNET couldn't/wouldn't recognize Kevin's address! Kevin, Could you clue me in on the CLASS_DISCONNECT you described? I've recently written such a beast, trying to DISCONNECT idle processes, instead of blowing them away, but have had some problems. I chose to go to the fiche and "emulate" the DCL DISCONNECT command using the IO$M_DISCON modifer. This seemed to work just fine, EXCEPT, DCL has an outstanding read request which must be cancelled, which I've done. BUT this TOO causes some problems, which we've learned to live with for the time being. Your write-up seems to imply you may have a different/better "back-door"! I'm very interested! Thanks, Denny Thury CSnet : THURY%MCOPN1@TI-EG VAX Systems Support ARPA : THURY%MCOPN1@TI-EG.CSNET Texas Instruments Incorporated McKinney, Texas