Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ucla-cs!zen!ucbvax!LLL-ICDC.ARPA!ivanovic%vaxr.DECnet
From: ivanovic%vaxr.DECnet@LLL-ICDC.ARPA ("VAXR::IVANOVIC")
Newsgroups: comp.lang.ada
Subject: Disassociating processes from terminals
Message-ID: <8707032040.AA24972@ucbvax.Berkeley.EDU>
Date: Wed, 1-Jul-87 17:31:00 EDT
Article-I.D.: ucbvax.8707032040.AA24972
Posted: Wed Jul  1 17:31:00 1987
Date-Received: Sat, 4-Jul-87 14:23:51 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: "VAXR::IVANOVIC" <ivanovic%vaxr.decnet@lll-icdc.arpa>
Distribution: world
Organization: The ARPA Internet
Lines: 25

Yakim Martillo (bloom-beacon!martillo@husc6.harvard.edu) writes

    ... With VMS and Multics its fairly hard to disassociate a process from the
    terminal. I think it may actually be impossible in the case of Mulics to
    disassociate the process completely.  I find this limitation sort of a
    pain.

Speaking for VMS, try using the RUN command, in particular, using the
qualifier "/DETACHED".  For example the command

    $ RUN /DETACHED /INPUT=some-DCL-command-file-spec /OUTPUT=a-log-file -
    	sys$system:loginout.exe

starts a new process using the invoker's UAF record, taking the input commands
from the command file "some-DCL-command-file" and sending the output to
"a-log-file".  It's pretty easy to use.  We do it all the time.

							-- Vladimir

P.S. I posted a question to you about the "fundamental entities" that UNIX,
VMS, and Multics use, and even though I saw the question on  INFO-ADA, I didn't
notice a reply from you.  I was away for a week of vacation and our
distribution node/network was down for a couple of days, so if you did reply,
would you send me a copy?  Thanks.
------