Path: utzoo!attcan!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Mike Khaw)
Newsgroups: comp.unix.wizards
Subject: Re: rsh environment
Message-ID: <26282@teknowledge-vaxc.ARPA>
Date: 2 Jan 89 19:32:12 GMT
References: <49@rpi.edu>
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 29

<49@rpi.edu>, by kyriazis@rpics (George Kyriazis):
+ In article <15215@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
+>
+>4BSD's `rsh' remote shell (not restricted shell) runs the login user's
+>shell.  If that shell is a `csh', it reads ~/.cshrc under the usual
+>restrictions for `csh -c' commands.
+>
+ 
+ then can you tell me why when I do   'rsh localhost ph'
+ where ph is my alias for 'ps aux | head' it says  'ph: Command not found' ??
+ I set up my aliases in my .cshrc.   Also when I do    rsh localhost alias
+ it doesn't show anything.  If I do rsh localhost printenv  it just shows
+ 4 shell variabls and not the tons I usually have.  Any ideas?

If you do "rsh localhost set" you will probably find that "term" and
"prompt" are not set.  So it looks like an rsh command runs a csh that
doesn't think it's an interactive shell (sorta makes sense).  Your
.cshrc probably contains tests for $prompt and/or $term being set.
Move the aliases, etc., that you want available to rsh commands outside
the test clause.

Disclaimer:  I get this behavior on Ultrix 2.2 and SunOS 3.x; your
environment may differ.

Mike Khaw
-- 
internet: mkhaw@teknowledge.arpa
uucp:	  {uunet|sun|ucbvax|decwrl|ames|hplabs}!mkhaw%teknowledge.arpa
hardcopy: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303