Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!ai-lab!life.ai.mit.edu!rearl From: rearl@gnu.ai.mit.edu (Robert Earl) Newsgroups: comp.sys.next Subject: Re: Bash 1.05 as login shell on NeXT Mach 2.0 Message-ID: Date: 29 Apr 91 23:07:23 GMT References: <7352@mace.cc.purdue.edu> Sender: news@ai.mit.edu Distribution: comp Organization: (EVIL!) Lines: 34 In-reply-to: abe@mace.cc.purdue.edu's message of 29 Apr 91 19:13:37 GMT In article <7352@mace.cc.purdue.edu> abe@mace.cc.purdue.edu (Vic Abell) writes: | In article rearl@gnu.ai.mit.edu (Robert Earl) writes: | >I recently compiled and installed bash 1.05 (including some bug fixes) | >and then tried to make it my login shell. I tried to test it out with | >an rlogin from a remote host and never got a prompt; I checked the | >process from another terminal and it was using 95% CPU, and wasn't | >connected to a controlling tty! | | The error is in rlogind, which fails to set a process group number for the | shell it invokes. Apparently this doesn't bother csh, which must supply a | process group number if none is set. Ksh doesn't, and probably the same | is true for bash. Vic's solution has solved about half my problem so far. He also mentioned using TIOCSPGRP to set the tty process group and I added that [after I found the following :(]. I can get a shell but the errors from stty and output of ps indicate bash hasn't connected to a tty yet. So whatnext? (Err, no pun intended :) rearl@watnxt3[3]% /bin/ps ux USER PID %CPU %MEM VSIZE RSIZE TT STAT TIME COMMAND rearl 16271 2.8 6.2 1.88M 512K ? S 0:05 -fixed-bash (fixed-bash) rearl 15783 0.0 6.7 2.19M 552K p2 S 0:20 emacs rearl 14610 0.0 1.0 1.34M 80K p2 SW 0:02 -csh (csh) rearl@watnxt3[6]% /usr/bin/tty /dev/ttypb Thanks to Vic, and thanx in advance to anyone who can help me out further here. --robert -- rearl@gnu.ai.mit.edu rearl@watnxt3.ucr.edu