From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from opus.INS.cwru.edu ([129.22.8.2]) by hawkwind.utcs.toronto.edu with SMTP id <75572>; Wed, 13 Feb 2002 16:11:31 -0500 Return-Path: chet@nike.ins.cwru.edu Received: from nike.ins.cwru.edu (nike.INS.CWRU.Edu [129.22.8.219]) by opus.INS.cwru.edu with SMTP (8.11.6+cwru/CWRU-3.9) id g1DKfr013005; Wed, 13 Feb 2002 15:41:53 -0500 (EST) (from chet@nike.ins.cwru.edu) Date: Wed, 13 Feb 2002 15:36:33 -0500 From: Chet Ramey To: pk@TechFak.Uni-Bielefeld.DE Subject: Re: non login "rc" needs customized environment Cc: rc@hawkwind.utcs.toronto.edu Reply-To: chet@po.CWRU.Edu Message-ID: <020213203633.AA70816.SM@nike.ins.cwru.edu> Read-Receipt-To: chet@po.CWRU.Edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-In-Reply-To: Message from pk@TechFak.Uni-Bielefeld.DE of Wed, 13 Feb 2002 14:21:43 -0500 (id <200202131921.UAA01849@grimsvotn.TechFak.Uni-Bielefeld.DE>) > We have been using "rc" as default login shell for more than 10 years now > with currently 1000+ users in our department. Every now and then, but > with increasing frequency recently we've felt uncomfortable with "rc"s handling > of $HOME/.rcrc. It's only processed if "rc" is a login shell, which is not > the case if you use rsh/ssh for calling commands on a remote system. > Unfortunately this prevents users from customizing their environment there, > especially the PATH variable. The environment can be modified with ssh, via ~/.ssh/environment. ssh also provides ~/.ssh/rc to run commands before the user's command is started. It's run by the user's login shell as taken from the password file. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet) Chet Ramey, CWRU chet@po.CWRU.Edu http://cnswww.cns.cwru.edu/~chet/