Xref: utzoo comp.unix.wizards:8628 comp.sys.hp:839
Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!pacbell!att!ihnp4!ihlpf!dwm
From: dwm@ihlpf.ATT.COM (Meeks)
Newsgroups: comp.unix.wizards,comp.sys.hp
Subject: Re: rcp failure due to echo
Summary: rcp and spawned shells
Keywords: rcp echo cshrc
Message-ID: <4812@ihlpf.ATT.COM>
Date: 19 May 88 19:50:43 GMT
References: <511@edsews.EDS.COM>
Distribution: na
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 19

> the 9000 series) and the command was failing miserably.  I should note that
> when I run my .cshrc I echo out a "This is the .cshrc executing message" 
> (probably lights are already going on over somebody's head out there 8-).
> Anyway, when I did an rcp, all I got was the first echo line of my .cshrc
> sent to stdout (even if I had two echo lines in the file, I only got one
> as output).  There was no error message and no file copied.  When the echoes
-----------------

RemoteCoPy sorta ( technical term, sorry ) logs you into the remote machine.
Remember that .xxxrc files are executed with each new shell. Thus, your
rcp is executing your remote .xxxrc before it makes any copies. Because
of the way rcp works, echos and stty stuff ( another technical term ) should
not be included in your .xxxrc. I have found this generally true of most
implementations. I have created a .xxxrc which uses a case statement to 
determine if I have come in remotely or not.

Dan Meeks, AT&T Bell Laboratories         *       +   ___----------^---------- 
dwm @ ...ihnp4!ihlpf!iecp1!dwm      *  ___________   /   >-------------------/
( 312 ) 416 - 5379                    (_========#_D_----/ .    *   `engage!  .
200 Park Plaza, Naperville, Il 60566      `--`==_______/     +    .       *