Description of problem:
When switching to runlevel 1 from runlevel 3, control of the serial console is passed directly to sushell or sulogin (configured in /etc/sysconfig/init). The serial console loses its terminal settings during the runlevel change, making it impossible to login via sulogin. Entering any key immediately kicks back an incorrect password response. sushell has similar problems but executing "reset" can fix that condition.

Version-Release number of selected component (if applicable):
initscripts-9.03.23-1.el6

How reproducible:
Always

Steps to Reproduce:
1. Configure a serial console in RHEL6, set SINGLE=/sbin/sulogin in /etc/sysconfig/init
2. Boot into runlevel 3, then switch to runlevel 1
3. Try entering the root password
  
Actual results:
Password input is not taken, sulogin immediately rejects any input. If sushell is specified instead, newlines do not work for output.

Expected results:
Should be able to enter password to sulogin. For sushell, the terminal should properly print newlines.

Additional info:
This does not occur when booting directly into a single mode serial console, only when switching from a higher runlevel.

Executing "stty sane" before "exec $SINGLE" in /etc/init/rcS-sulogin.conf works around this problem by setting certain terminal defaults.

I had considered filing a bug against sysvinit-tools because sulogin is not resetting the terminal, but this issue also affects sushell which simply passes control to the default shell. The easiest fix may be addressing this in initscripts.