remote processes started with rsh can be killed unintentionally
der Mouse
mouse at mcgill-vision.UUCP
Tue Sep 3 17:24:05 AEST 1985
> 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
More information about the Comp.bugs.4bsd.ucb-fixes
mailing list