Hi Eric, > It ought to be > > /sbin/udevadm triger > /sbin/udevadm settle --timeout=300 > > depending on your udev version. > > todo++ :-)
Thanks a lot for your hint, now initng does not hang anymore for several seconds at 7% of the initialization of my Debian Lenny installation :-) For documentation purposes, the file /etc/initng/system/udev.i now contains the following lines: # wait for the udevd childs to finish # /sbin/udevsettle # Request device uevents /sbin/udevadm trigger # Watch the udev event queue, and exit if all current events are handled /sbin/udevadm settle --timeout=300 Well, I am no udev expert, the above-mentioned comments about the udevadm options are quotes from the udevadm manpage ;-) There are two other issues with regard to the initialization of my Debian Lenny installation by initng: 1. KDM daemon started twice At the end of the boot and initng initialization process, the KDE login screen is displayed for some seconds, but then it dissappears, instead a black screen is visible, and then the login screen is displayed again. It seems as if KDM is loaded, then it gets terminated, then it gets started again. How can I prevent initng from terminating the first session of KDM and starting KDM again? 2. After the system is up, three services need to be "zapped" After the system is up, if I apply ngc -s, the following three services are shown with a status in red letters. Obviously they could not be successfully loaded: 15:06:14 R runlevel/default : START_DEPS_FAILED 15:05:59 S service/speedstep : SERVICE_FAIL_START_RCODE 15:06:00 S net/eth0 : SERVICE_FAIL_START_RCODE If I apply ngc --zap <service> to each of them, and then again ngc -s, then I notice the following: - The runlevel/default service has the status "DAEMON_RUNNING" - The speedstep service is not listed anymore, instead the system/modules/speedstep_centrino service is listed as "SERVICE_DONE" - The net/eth0 service is not listed anymore. But my Internet connection is still working. If I do not "zap" them, these three services are specified on the screen at the end of the shutdown process, delaying the shutdown process for 15 seconds. How can I prevent initng from generating FAIL* service statusses while the system boots? Best regards, Jens -- _______________________________________________ Initng mailing list [email protected] http://jw.dyndns.org/mailman/listinfo/initng
