Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site mcgill-vision.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!bbnccv!bbncca!linus!philabs!micomvax!musocs!mcgill-vision!mouse
From: mouse@mcgill-vision.UUCP (der Mouse)
Newsgroups: net.bugs.4bsd
Subject: Re: remote processes started with rsh can be killed unintentionally
Message-ID: <135@mcgill-vision.UUCP>
Date: Tue, 3-Sep-85 03:24:05 EDT
Article-I.D.: mcgill-v.135
Posted: Tue Sep  3 03:24:05 1985
Date-Received: Sat, 7-Sep-85 05:52:11 EDT
References: <4831@allegra.UUCP>, <145@graffiti.UUCP>
Organization: McGill University, Montreal
Lines: 27

> Repeat-By:
> 	$ rsh presto "troff big-job" &
> 	$ [ at this point if you type ^C, the troff will be interrupted ]

     This may not be a bug.  I believe rsh will have  your terminal open
in case you type something so it can get sent to the remote job (someone
correct me if sh  (I assume  sh  from the  $  prompt) uses /dev/null  or
something equally stupid for stdin for jobs run with &).  So the ^C  may
be doing exactly what it should.    I do know under 4.2bsd with the csh,
if  I try  to 'rsh  somehost  somecommand &' rsh  will  stop immediately
because  it  is in the  background  when  it tries to open the tty.  Try
doing

	rsh presto troff big-job < /dev/null

(don't  quote the < sign).  Then rsh  will get its  stdin from /dev/null
instead of your tty and *maybe* it will work.

		Maybe.
-- 
					der Mouse

{ihnp4,decvax,akgua,etc}!utcsri!mcgill-vision!mouse
philabs!micomvax!musocs!mcgill-vision!mouse

Hacker: One responsible for destroying /
Wizard: One responsible for recovering it afterward