Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ames!ucbcad!ucbvax!GRIN2.BITNET!MCGUIRE
From: MCGUIRE@GRIN2.BITNET
Newsgroups: comp.os.vms
Subject: RE: VAX LISP bug
Message-ID: <8708081028.AA27424@ucbvax.Berkeley.EDU>
Date: Thu, 6-Aug-87 13:04:00 EDT
Article-I.D.: ucbvax.8708081028.AA27424
Posted: Thu Aug  6 13:04:00 1987
Date-Received: Sun, 9-Aug-87 10:50:05 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 12

VAX BASIC used to do this too.  If you went into the BASIC interpreter,
typed in a short program that wrote to the terminal such as:
10 PRINT "-----------------------------------------------------"
20 GOTO 10
30 END
And then ran it, then dropped modem signals, the process would stay around. In
fact, the program would be halted, but BASIC trapped the condition and put you
back into the interpreter.  If you found someone else logged in this way, you
could use the `$' subprocess escape to get to DCL and do nasties.  You had to do
it that way, because if you exited from the interpreter (running the image down)
then the process would say `data set hangup' and disappear.
---- Ed McGuire, Systems Coordinator, Grinnell College, MCGUIRE@GRIN2.BITNET