Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!uw-beaver!zephyr.ens.tek.com!wrgate!amadeus!michaelp
From: michaelp@amadeus.WR.TEK.COM (Michael Prusynski)
Newsgroups: comp.unix.shell
Subject: Re: rsh guru req'd!
Keywords: rsh
Message-ID: <5830@wrgate.WR.TEK.COM>
Date: 29 Apr 91 21:46:48 GMT
Sender: news@wrgate.WR.TEK.COM
Lines: 27


In article <6226@iron6.UUCP> yeates@motcid.UUCP (Tony J Yeates) writes:
>[The problem I have is that when I rsh scripts (which I do not own)
>they fail, because some of the commands that they use cannot
>be found (doing "rsh silicon echo '$PATH'" reveals my path is
>severely truncated...":/usr/ucb:/bin:/usr/bin").]

I've made an executable shell script in my HOME directory on the remote 
machine(s) called:  do
which contains:

PATH=/u/michaelp/bin:/usr/local:/usr/ens/bin:/usr/tek:/usr/ucb:/bin:/usr/bin
exec $@

Then you can type:
rsh silicon do echo '$PATH'

to check the PATH, or something more useful like:
rsh silicon do some-command-in-a-non-standard-path


It works for me!
-----
Michael Prusynski (michaelp@amadeus.WR.TEK.COM)   Phone: (503) 629-3062
USMail:  Tektronix Inc., MS 92-304, PO Box 4600, Beaverton, OR 97076    __o
  UUCP:  ...!uunet!tektronix!amadeus.WR.TEK.COM!michaelp               -\<,
  ARPA:  @RELAY.CS.NET:michaelp@amadeus.WR.TEK.COM                ....O/ O