Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!ucbvax!edison.UUCP!jso
From: jso@edison.UUCP.UUCP
Newsgroups: mod.computers.vax
Subject: Re: Re: Toggle Interactive/Detached
Message-ID: <8605231401.AA17155@edison.UUCP>
Date: Fri, 23-May-86 10:01:01 EDT
Article-I.D.: edison.8605231401.AA17155
Posted: Fri May 23 10:01:01 1986
Date-Received: Tue, 3-Jun-86 21:35:10 EDT
References: <8605131052.AA20508@ucbvax.Berkeley.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21
Approved: info-vax@sri-kl.arpa

> First off, I don't understand what you mean by a "detached process".  In VMS
> usage, a detached process is one that is not a subprocess.  When you log in,
> your top level process is detached.  You may be referring to a disconnected
> process, but that doesn't make much sense either.

Probably "Detached processes that are not interactive", i.e., those
that are created by a RUN/misc-qualifiers.  They certainly wouldn't
return INTERACTIVE from f$mode; probably BATCH or OTHER....

> As for receive broadcast/breakthru writes:  Those are implemented in the
> terminal driver.  If the program isn't connected to a terminal, there is no
> way for it to receive broadcast messages.

Exactly.  Broadcast messages are sent to a terminal, not a process....

	John Owens
	edison!jso%virginia@CSNet-Relay.ARPA		[old arpa]
	edison!jso@virginia.EDU				[w/ nameservers]
	jso@edison.UUCP					[w/ uucp domains]
	{cbosgd allegra ncsu xanth}!uvacs!edison!jso	[roll your own]