Path: utzoo!attcan!uunet!husc6!bloom-beacon!gatech!purdue!decwrl!hplabs!hpda!hpcupt1!hpcuhb!hpihoah!bruce
From: bruce@hpihoah.HP.COM (Bruce LaVigne)
Newsgroups: comp.sys.hp
Subject: Re: rcp failure due to echo
Message-ID: <5030001@hpihoah.HP.COM>
Date: 13 May 88 15:55:43 GMT
References: <511@edsews.EDS.COM>
Organization: Hewlett Packard, Cupertino
Lines: 21

I am posting this because the mailer bounced it...

In reference to your rcp problem with echo, the reason it fails is that rcp
can only tell if there was an error on the remote end if it recieves some
(read any) data back from the host on stdout/stderr.  Therefore, your echo
told rcp there was an error in connecting to the host, and it stopped.  We
saw the same problem here, and fixed it by checking for interactive in the
.cshrc before doing the echo - using the "if $?prompt" construct.  Rcp is
not considered interactive, so the echo doesn't happen, and everyone is
happy.  Try it out!

-bruce

          Bruce LaVigne

          ARPA:    bruce%hpda@hplabs.hp.com
          UUCP:    {ucbvax,hplabs}!hpda!bruce
          USnail:  c/o Hewlett-Packard m/s 42L8
                   19447 Pruneridge Avenue
                   Cupertino, CA  95014
          Phone:   (408)447-6279 work