Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!sunybcs!boulder!forys
From: forys@sigi.Colorado.EDU (Jeff Forys)
Newsgroups: comp.unix.questions
Subject: Re: rsh, rcp and the message "Where are you?"
Message-ID: <2856@sigi.Colorado.EDU>
Date: Sat, 7-Nov-87 08:07:52 EST
Article-I.D.: sigi.2856
Posted: Sat Nov  7 08:07:52 1987
Date-Received: Mon, 9-Nov-87 06:41:02 EST
References: <173@tarski.quintus.UUCP>
Reply-To: forys@boulder.Colorado.EDU (Jeff Forys)
Organization: University of Colorado, Boulder
Lines: 25
Keywords: BSD, SUN OS
Summary: rsh(1C) and rcp(1C) use shell on target machine.

I have sent mail on this to a couple people, I now present it here
in hopes that it will forever be remembered.  :-)

In article <173@tarski.quintus.UUCP> (W. Gregg Stefancik) writes:
> When I do a rsh or rcp from certain accounts I get the message
> "Where are you?" and then the remote command usually fails.

Rsh(1) invokes rshd(8C) on the target machine, this in turn starts up a
shell to execute your command.  Likewise, rcp(1C) (actually anything that
uses rcmd(3)) invokes rexecd(8C) on the target host, again starting up a
shell to execute your command.  Remember, by default, when a C shell is
started, your ~/.cshrc is sourced and any commands therein are executed.

With that out of the way, the error message "Where are you?" comes from
biff(1) when improperly placed in ~/.cshrc on the target machine.  Biff(1)
displays this message when it is unable to find its controlling terminal.
You should move the `biff' command to your ".login" to solve the problem.

A second, more obscure fix, is to put "if (! $?prompt) exit" near the top
of your ~/.cshrc.  Doing this prevents the remainder of your .cshrc from
being executed when not running in interactive mode (e.g. using a remote
shell).  This `feature' is used to expedite start up of remote shells...
---
Jeff Forys @ UC/Boulder Engineering Research Comp Cntr (303-492-4991)
forys@boulder.Colorado.EDU  -or-  ..!{hao|nbires}!boulder!forys