Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.questions
Subject: Re: why no .kshrc file?
Keywords: ksh history sh csh
Message-ID: <11344@smoke.BRL.MIL>
Date: 19 Oct 89 11:13:24 GMT
References: <262@zeek.UUCP> <1287@virtech.UUCP> <30996@news.Think.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 8

In article <30996@news.Think.COM> barmar@kulla (Barry Margolin) writes:
>How do you arrange for $ENV to get set if the shell isn't a descendent
>of a login shell?  For instance, shells started by "rsh" aren't login
>shells.

I general solve problems like this by telling rsh to invoke the "env"
command on the remote end (with appropriate arguments).  If you don't
have "env" or equivalent, that's YOUR problem :-).