[BusyBox 0001244]: (init) inittab handling broken in revision 17937

bugs at busybox.net bugs at busybox.net
Fri Mar 2 20:38:13 UTC 2007


A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1244 
====================================================================== 
Reported By:                espakman
Assigned To:                BusyBox
====================================================================== 
Project:                    BusyBox
Issue ID:                   1244
Category:                   Other
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             03-01-2007 13:14 PST
Last Modified:              03-02-2007 12:38 PST
====================================================================== 
Summary:                    (init) inittab handling broken in revision 17937
Description: 
Since revision 17937 not all items in the inittab are executed.

My inittab file:

::sysinit:/etc/init.d/rcS
::wait:/etc/init.d/rc 2

tty1::respawn:/sbin/getty 38400 tty1
tty2::respawn:/sbin/getty 38400 tty2

::restart:/sbin/init

::shutdown:/etc/init.d/rc 0


The "wait" (rc 2) and "shutdown" (rc 0) scripts are not executed after rev
17937, also if I replace the "wait" with a second "sysinit" this line is
not executed. Running rc 0 or rc 2 by hand or using a busybox before rev
17937 works fine.

Libc: uClibc-0.9.28
gcc: gcc-3.3.3

====================================================================== 

---------------------------------------------------------------------- 
 espakman - 03-02-07 12:38  
---------------------------------------------------------------------- 
The problem seems to be a bit different. No init startup/shutdown output is
shown on the console anymore and some daemons won't start up on boot time
with this revision (maybe they need a controlling tty?). Some examples of
daemons that won't start on init: dnsmasq and ulogd 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-01-07 13:14  espakman       New Issue                                    
03-01-07 13:14  espakman       Status                   new => assigned     
03-01-07 13:14  espakman       Assigned To               => BusyBox         
03-02-07 12:38  espakman       Note Added: 0002196                          
======================================================================




More information about the busybox-cvs mailing list