Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!husc6!rutgers!lll-crg!nike!ucbcad!ucbvax!YALE.ARPA!LEICHTER-JERRY From: LEICHTER-JERRY@YALE.ARPA Newsgroups: mod.computers.vax Subject: Re: Disconnect Message-ID: <8611030135.AA03165@ucbvax.Berkeley.EDU> Date: Sun, 2-Nov-86 20:35:18 EST Article-I.D.: ucbvax.8611030135.AA03165 Posted: Sun Nov 2 20:35:18 1986 Date-Received: Tue, 4-Nov-86 01:47:18 EST Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Organization: The ARPA Internet Lines: 21 Approved: info-vax@sri-kl.arpa Disconnect dosen't work! There is something fishy about Disconnect, it doesn't hibernate the disconnected process as is should which leads to some tire- some consequenses. For instance the INACTIVE-Daemon removes disconnected processes when it's activated every 10 minutes or so. Or in other words, Disconnect doesn't work on systems where INACTIVE is running. Why do you claim DISCONNECT doesn't work? It's INACTIVE that doesn't work. No one ever claimed that DISCONNECT caused processes to hibernate; why "should" it do this? There are SEVERAL VMS states that correspond to long- term waits of different sorts - HIBERNATE is just one of them. I don't know off-hand what state DISCONNECT'ed processes go into, but if I had to guess I'd say LEF. DISCONNECT works fine on systems with INACTIVE running. INACTIVE incorrectly kills certain processes on systems where DISCONNECT is used! -- Jerry -------