Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!mordor!sri-spam!rutgers!pbox!okstate!gregg
From: gregg@a.cs.okstate.edu (Gregg Wonderly)
Newsgroups: comp.os.vms
Subject: Re:  Odd subprocess behaviour
Message-ID: <3197@okstate.UUCP>
Date: 22 Feb 88 15:56:10 GMT
References: <2746@enea.se>
Organization: Oklahoma State Univ., Stillwater
Lines: 28

in article <2746@enea.se>, sommar@enea.se (Erland Sommarskog) says:
> 
> Jerry Leichter writes:
>>	...[I]f you create a subprocess and attach to it, then re-attach to
>>	the parent process, then spawn a second subprocess and attach to it,
>>	THEN kill the first subprocess with a STOP command from t'other (still
>>	with me?), VMS can't decide which of the remaining two processes
>>	(parent and 2nd child) is attached to the terminal!  You get a mixture
>>	of prompts, and it isn't clear where the things you type go.
>>	...

Another not so nice behavior happens when you logon to a terminal set /NOMODEM,
and then spawn a subprocess (a kept editor is an example).  Attach back to the
parent process from the subprocess, and DISCONNECT.  Later, you logon to a
terminal set /MODEM, and ATTACH to the subprocess.  BINGO, DTR gets dropped,
and you are DISCONNECTED.  Log back on, and as soon as you CONNECT to the
DISCONNECTED process, again, you are DISCONNECTED.  Now you logon one more time,
and all is well.  The subprocess starts up, and you do whatever.  Then you
try to attach back to the parent.  BINGO you are DISCONNECTED again.  Log back
on and CONNECT to the DISCONNECT'd process, and all is well.  This is less
than optimal, no?

-----
Gregg Wonderly
Department of Computing and Information Sciences
Oklahoma State University

UUCP:      {cbosgd, ihnp4, rutgers}!okstate!gregg
Internet:  gregg@A.CS.OKSTATE.EDU