Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!hao!gatech!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!iuvax!bsu-cs!cfchiesa
From: cfchiesa@bsu-cs.UUCP (Sir Xetwnk)
Newsgroups: comp.os.vms
Subject: Re: Odd subprocess behaviour
Message-ID: <2203@bsu-cs.UUCP>
Date: 24 Feb 88 16:31:44 GMT
References: <8802151119.AA27861@ucbvax.Berkeley.EDU> <2746@enea.se>
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 38


 Here's another baddie.

 I did the following the other day with the following results:

  1) Enter an LSE session in my main process.

  2) SPAWN a subprocess to do whatever it was I wanted to do....

  3) ATTACH back to the parent process, leaving the subprocess out there.

  4) Successfully ATTACH back and forth from LSE-in-parent-process to 
     DCL-in-subprocess, several times.

  5) Terminate LSE session with EXIT command, leaving subprocess out there.

  6) Successfully attach back and forth from DCL-in-parent-process to 
     DCL-in-subprocess, several times.

  7) Issue LO (or EOJ) command from DCL-in-subprocess, with intent to have 
     it die and leave me back in the parent process.

    Instead, it killed the Subprocess and "hung" the parent.  It sat there
    in HIB state (I logged on again and did a SHO PROC/CONT) and nothing I
    could do (tried my li' SYS$WAKE utility, to no avail) affected it in the
    least.  I finally had to do a STOP/ID from the second login, to remove 
    the original nogoodnik from the system.

Any thoughts on what the $&%$&'@&!! happened?  What a pain in the ... neck!

   Chris Chiesa, Senior, CS Dept., Ball State Univrsity, Muncie, IN

 

-- 
<><><><><><><><><><><><><><><><><><><><><><><><><><><><> Chris Chiesa <><><><><>
<> {ihpn4|seismo}!{iuvax|pur-ee}!bsu-cs!cfchiesa                              <>
<> cfchiesa@bsu-cs.UUCP                                                       <>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>