Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!stanford.edu!msi.umn.edu!cs.umn.edu!mermaid!cattelan
From: cattelan@mermaid.micro.umn.edu (Russell Cattelan)
Newsgroups: comp.sys.next
Subject: Re: shells and 2.0 rlogind
Message-ID: <1991Apr10.223326.4021@cs.umn.edu>
Date: 10 Apr 91 22:33:26 GMT
References: <14378@helios.TAMU.EDU>
Sender: news@cs.umn.edu (News administrator)
Organization: University of Minnesota, Minneapolis: Under Grad Workstation Lab.
Lines: 16
Nntp-Posting-Host: mermaid.micro.umn.edu

haustin@cs.tamu.edu (Harold E Austin Jr.) 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