Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.unix.shell
Subject: Re: rsh guru req'd!
Keywords: rsh
Message-ID: <3797@sixhub.UUCP>
Date: 25 Apr 91 03:00:08 GMT
References: <6226@iron6.UUCP> <1991Apr23.003518.4442@leland.Stanford.EDU>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Distribution: comp.unix.shell
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 24

In article <1991Apr23.003518.4442@leland.Stanford.EDU> dkeisen@leland.Stanford.EDU (Dave Eisen) writes:

| It isn't, and there is no real way to get around this. What I usually
| do when I want to pass something to a remote shell is to explicitly set the 
| environment variable in the command, something like (using /bin/sh as the 
| login shell):
| 
| rsh silicon "VARIABLE=$VARIABLE; export VARIABLE; command-line"

  Not needed. When a variable is defined on a command line *not*
separated by a colon it is exported to that command only. If you were
were doing more than one command you would do it as you have shown, and
forgive me if you simplified and knew this, but for the case you show,
the simplified form:

    rsh silicon "VARIABLE=$VARIABLE command-line"

works just fine. I avoid typing at every chance because I do it so
rapidly but inaccurately.
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -me