Subject: Re: rcp problems
To: None <netbsd-help@netbsd.org>
From: Timothy A. Musson <Timothy.Musson@zin-tech.com>
List: netbsd-help
Date: 10/02/2000 15:00:43
No, there is no "$TERM" in .cshrc.

However, there *was* a $TERM in .tcshrc.
Oops. :)

Thanks!


At 02:48 PM 10/2/00 , you wrote:
>On Mon, 2 Oct 2000, Timothy A. Musson wrote:
>
>: "rcp <filename> <user>@<host>:"  produces "TERM: Undefined variable",
>: and the file is not copied (previously, output from .cshrc was confusing
>: rcp, but that problem was rectified).
>
>I think you're still getting output from .cshrc, because indeed, $TERM is
>not set when using rsh (the rcp underlying protocol), and your .cshrc is
>probably outputting "TERM:  Undefined variable" because $TERM is listed
>somewhere in .cshrc.
>
>: "rcp <user>@<host>:<filename> ."  produces
>: "rcp: protocol error: mtime.sec not delimited"
>
>See above; probably same answer.
>
>-- 
>-- Todd Vierling <tv@wasabisystems.com>  *  http://www.wasabisystems.com/
>-- Speed, stability, security, and support.  Wasabi NetBSD:  Run with it.
> 
--
Timothy A. Musson
NASA's John Glenn Research Center at Lewis Field
Software Engineer (Zin Technologies)
SAMS-II Project               It's not the size of the dog in the fight,
216-977-0608                  It's the size of the fight in the dog.
mussont@zin-tech.com