XRAYOLLE@SEMAX51.BITNET (10/30/86)
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.
If anyone should wonder; INACTIVE is a daemon process that removes
inactive (nonhibernating) processes/users after a predefined time,
say 10 minutes. I.e. INACTIVE is activated every 10 minutes.
Please respond to me directly because I'm not a reader of INFO-
VAX. (I will post a summary to the net)
My adress is: XRAYOLLE@SEMAX51.BITNETLEICHTER-JERRY@YALE.ARPA (11/03/86)
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
-------