init not going to runlevel 3 after exiting sulogin on RHEL5 if configured to spawn getty
Issue
- Modifications were made to /etc/inittab to allow for other gettys to run in single user mode:
# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
# Run gettys in single-user - keep separate from above to force logout
x1:1:respawn:/sbin/mingetty tty1
x2:1:respawn:/sbin/mingetty tty2
x3:1:respawn:/sbin/mingetty tty3
x4:1:respawn:/sbin/mingetty tty4
x5:1:respawn:/sbin/mingetty tty5
x6:1:respawn:/sbin/mingetty tty6
# Added for single-user mode password
~~:S:wait:/sbin/sulogin
When exiting sulogin with these entries in inittab, init does not go to runlevel 3.
Commenting out the entries that run during runlevel S fixes this issue; exiting from sulogin prompts init to go to runlevel 3.
Environment
- Red Hat Enterprise Linux 5
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.