From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) Description of problem: After doing an init 1 command and getting to the shell things do not work right. I can type ls a few times and then start getting errors like: s command not found or l command not found. So it seems like keystrokes are being lost by the shell. Also an error message sometimes prints right before I get to the shell prompt. The message is: sh: no job control in this shell sh-2.05# Then when I hit enter the prompt changes to: [root@cvs root]# I have this problem on three systems running Red Hat 7.2. Two systems were upgraded and one was a fresh install. All systems have all patches applied to them that had been released as of 25-Oct-01 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. login as root 2. type: init 1 3. type: ls <enter> a few times and notice error Actual Results: Error message from shell. Appears that some keystrokes are being lost. Expected Results: No keystrokes would be lost and commands would execute. Additional info:
Which kernel, exactly, are you running?
kernel-2.4.9-7.i686 on two of the machines. kernel-2.4.9-7smp.i686 on one. Everything works fine unless I go into single user mode.
I realized the same error today: it looks like the directory or environment gets changed with two instances (a popd or pushd problem?). I realized that in comparison with a 7.1 system the 7.2 one does print sh: no job control in this shell right before the root prompt. so here is my screen output: sh-2.05# ls anaconda-ks.cfg [root@neith root]# ls bin dev home lib mnt proc sbin usr boot etc initrd lost+found opt root tmp var sh-2.05# ls anaconda-ks.cfg [root@neith root]# ls bin dev home lib mnt proc sbin usr boot etc initrd lost+found opt root tmp var and so on (we see the two different directories).
downgrading to initscripts and bash from 7.1 doesn't help either; BTW, kernel here is 2.4.9-13 from errata updates... take care Andreas
I have the same problem; it actually appears that two shells are running at the same time and some input characters go to each of the two shells! Ewww...
*** This bug has been marked as a duplicate of 54865 ***
please reopen because # 54865 is assigned to Red Hat Linux - 7.1
*** Bug 46223 has been marked as a duplicate of this bug. ***