Path: utzoo!attcan!uunet!netagw!samt19!hqda-ai!cos!hadron!decuac!shlump.nac.dec.com!decwrl!wuarchive!cs.utexas.edu!rice!uw-beaver!tektronix!reed!pzbaum!omepd!merlyn
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.unix.questions
Subject: Re: Pass environment through rlogin
Message-ID: <5254@omepd.UUCP>
Date: 23 Nov 89 01:00:13 GMT
References: <696@cs.wmich.edu> <1989Nov21.040936.10463@athena.mit.edu>
Sender: news@omepd.UUCP
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Organization: Stonehenge; netaccess via Intel, Hillsboro, Oregon, USA
Lines: 37
In-reply-to: jik@athena.mit.edu (Jonathan I. Kamens)

In article <1989Nov21.040936.10463@athena.mit.edu>, jik@athena (Jonathan I. Kamens) writes:
|   I don't believe there's any way to do this with the standard rlogin.
[describes a couple of hacks...]
|   People have been talking about writing an rlogin that transfers
| arbitrary environment variables over the connection for a long time
| now.  I wonder when it'll happen :-)

Of course, if the source and target machines have shared NFS-mounted
home directories, you can do something like:

(
printenv | sed 's/\(.*\)=\(.*\)/setenv \1 \2/' >~/.$$
setenv TERM ~/.$$
rlogin foosys
)

and in .login, have:

switch ($TERM)
case /*:
	set x=$TERM; source $x; rm -f $x
	breaksw
endsw

Of course, I've glossed over:
(1) metachars in the ~.$$ file
(2) not passing *all* the environment
(3) this untested code not working

but you can see the general idea.

Just another multiple system hacker,
-- 
/== Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ====\
| on contract to Intel's iWarp project, Hillsboro, Oregon, USA, Sol III  |
| merlyn@iwarp.intel.com ...!uunet!iwarp.intel.com!merlyn	         |
\== Cute Quote: "Welcome to Oregon... Home of the California Raisins!" ==/