From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from odin.INS.CWRU.Edu ([129.22.8.102]) by archone.tamu.edu with SMTP id <22534>; Tue, 6 Aug 1991 15:56:54 -0500
Received:  by odin.INS.CWRU.Edu (5.65b+ida+/CWRU-1.4-ins)
	id AA22715; Tue, 6 Aug 91 16:56:13 -0400 (from chet for rc@archone.tamu.edu)
Date: Tue, 6 Aug 1991 15:54:01 -0500
From: Chet Ramey <chet@odin.INS.CWRU.Edu>
To: donn@milton.u.washington.edu
Subject: Re: login shells
Cc: rc@archone.tamu.edu, chet@odin.INS.CWRU.Edu
Reply-To: chet@po.CWRU.Edu
In-Reply-To: Message from donn@milton.u.washington.edu of Tue, 6 Aug 1991 11:10:43 -0500
Message-Id: <9108062054.AA22708.SM@odin.INS.CWRU.Edu>
Read-Receipt-To: chet@po.CWRU.Edu

> > I think rshd is broken.
> 
> How should it work?  Would it be OK with you, if rshd exec'd commands
> with "-" prefixed to the shell name in argv[0], thus causing them to
> be "logins"?  That will force people who exec stty etc. in .rcrc to
> bracket that stuff with an interactivity test, but it's fairly
> straightforward.

I like the 10th Edition method of putting a special variable in the
environment of the invoked shell (REMOTE= or REMOTEHOST=otherhost or
something like that).

Chet

--
``Someday soon, I'm gonna tell the world about the crying game...''

Chet Ramey			  Internet: chet@po.CWRU.Edu
Case Western Reserve University	  NeXT Mail: chet@macbeth.INS.CWRU.Edu