Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!helios!haustin
From: haustin@cs.tamu.edu (Harold E Austin Jr.)
Newsgroups: comp.sys.next
Subject: Re: shells and 2.0 rlogind (SOLUTION)
Message-ID: <14489@helios.TAMU.EDU>
Date: 11 Apr 91 00:23:34 GMT
References: <14378@helios.TAMU.EDU> <1991Apr10.223326.4021@cs.umn.edu>
Sender: usenet@helios.TAMU.EDU
Organization: Computer Science Department, Texas A&M University
Lines: 24

cattelan@mermaid.micro.umn.edu (Russell Cattelan) writes:
+ > With this shell, users can login at the console, and rsh and telnet to a 
+ > 2.0 machine.  However, if such a user attempts to _rlogin_ to a 2.0 NeXT,
+ > the shell hangs before sourcing .cshrc and .login (and runs up to 99% CPU!).
+ > I discovered today that the problem also exists for users with /bin/tcsh as
+ > their default shell.
+ 
+ Yes this is a anoying like *BUG* in 2.0 
+ To fix this replace /bin/login and /usr/etc/rlogind with the 1.0 binaries
+ That is you have 1.0 copies around.
+ 
+ This fixed the problem with tcsh and should fix the problem with your shell.
+ 
+ -Russell Cattelan
+ cattelan@cs.umn.edu

Yep, it worked!  And it also fixed another 2.0 rlogin problem: /.rhosts was
ignored when root tried to rlogin to a 2.0 machine.  Always asked for a passwd.
By downgrading to 1.0 binaries for /bin/login and /usr/etc/rlogind, we killed
two bugs with one stone.  :)

Thanks,
Harold Austin
(haustin@cs.tamu.edu)