From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Description of problem:
When I first installed (fresh) RH 7.1 directly from CD /etc/inittab was
read properly. But when I updated my system from RHN /etc/inittab was not
read at all during bootup & kill -HUP 1 & init q. Looks like /etc/rc.d/rc
works but mingetty does not appear when I do ps auxw.
Steps to Reproduce:
1. Reboot many times
2. Tried to insert TT:123456:respawn:sleep 60 into /etc/inittab and do
kill -HUP 1
3. ps auxw
Actual Results: ps auxw doesn't show any mingetty and new entries
in /etc/inittab. To be specific, I need svscan to run for every
Expected Results: All default entries in /etc/inittab and newly inserted
entries should work when reboot & kill -HUP 1 & init q.
# My /etc/inittab file
# System initialization.
# Things to run in every runlevel.
# Trap CTRL-ALT-DELETE
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# When our UPS tells us power has failed, assume we have a few minutes
# of power left. Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.
pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"
# If power was restored before the shutdown kicked in, cancel it.
pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"
# Run gettys in standard runlevels
# Run xdm in runlevel 5
# xdm is now a separate service
# Added by Aznidin, Jul 5, 2001
SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin
svscan /service </dev/null >/dev/console 2>/dev/console
Is it exactly like above (i.e., is there a newline in the SV entry?)
I can't reproduce this here. Can you post your inittab as an attachment?
It's not sysV init bug but I ran a process in rc.local that keep init from
performing further execution (forgot to append the &). To be exact, it got
stuck in /etc/rc 5 command that runs S**local. That's why all the mingetty +
new inittab entries never execute. I co-locate my server somewhere that I could
not reach; therefore I could not see the error msg on the console while booting
that should show some failure point when executing rc.local. dmesg didn't help
me much. I figured this out from ps auxw.
Sorry & Thanks anyway.