Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!whuxl!houxm!mhuxt!mhuxr!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Re: program to do a "disconnect"
Message-ID: <7696@ucbvax.ARPA>
Date: Sun, 2-Jun-85 03:07:31 EDT
Article-I.D.: ucbvax.7696
Posted: Sun Jun  2 03:07:31 1985
Date-Received: Mon, 3-Jun-85 06:08:11 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 16

From: Kevin Carosso <engvax!KVC@cit-vax>

I wrote such a program.  It issues an I/O function to the terminal of
your choice that causes it to disconnect from it's job.  This, of
course, requires the SHARE privilege.  Only problem is that the I/O
request to disconnect gets queued behind any outstanding requests
that the terminal may have.  Thus, the job doing the disconnect hangs
until the target finishes up it's current I/O request.  Needless to
say this is less than desirable when the other terminal is idle.

The only solution I know of to this problem is to issue a special kernel
AST on the target process and do a $CANCEL on the channel.  I'll try
this when I get back to work from DECUS and see if it works.

	/Kevin Carosso              engvax!kvc @ CIT-VAX.ARPA
	 Hughes Aircraft Co.