Hi, First of all the error message "Error connecting to initng socket" usually means that initng has crashed. This used to be a problem on my system too, until version 0.6.10.2 came out, which fixed some amd64-specific bugs.
During my experience with initng I also found out that there are some plugins that one must have to have things working and some, that are known to cause trouble (dbus_event for example). I'm using gentoo and based on the past experience I've established a set of plugins, that are working properly on my system: [ebuild R ] sys-apps/initng-0.6.10.2 USE="busybox check_ro debug -as_init -cmake_color_makefile -count_me -force_nocolor" INITNG_PLUGINS="also bash_launcher chdir chroot conflict cpout critical ctrlaltdel debug_commands envparser fmon fstat idleprobe initctl interactive iparser last limit lockfile logfile netdev netprobe ngc4 nge pause provide reload renice rlparser simple_launcher stcmd stdout suid syncron syslog sysreq unneeded -daemon_clean -dbus_event -find -history -ngcs -selinux -service_file -usplash" 0 kB [1] I'm not such an expert in initng to tell you what influence each plugin has, but this setup has worked for me for some time and I'm happy with it. Regards Krzysztof Hans Hohenfeld pisze: > On Mon, Feb 04, 2008 at 03:30:06PM +0100, Helge Hafting wrote: > >> I have used initng on debian for some time. >> I used initng 0.6.7-1 for a long time, because >> that was all I could get packaged for amd64 debian. >> (There are newer packages, but only for i386 it seems.) >> >> This version has various problems: >> * fails to bring up wlan0, something "ifup wlan0" usually will do >> * sometimes long delays waiting for udev, but I use initng to boot *faster* >> * trouble with X crashing a couple of times during boot, but perhaps >> that is an X problem? >> * loadkeys always fails. Not a initng problem though. >> * After a handful of "ngc" commands, I get the dreaded "Error connecting >> to initng socket" and can't shutdown or do anything useful with ngc :-( >> >> So I finally downloaded the source for initng 0.6.10.2, and compiled it. >> I rebooted after "make install" and now ngc doesn't work at all. >> "Error connecting to initng socket" at the first try - everytime. >> >> >> Inability to reboot or bring up additional services makes initng useless >> for me. Is there a known way out of this, or will I have to >> look at other sysv init replacements? I liked the quick parallel startup, >> of initng, but I also need something that works. >> >> Helge Hafting >> -- >> > > Hi, > > I got the same problem here since my last system update (gentoo). I'm > using initng-0.6.10.2 and initng-ifiles-0.1.4. I don't know if there is > a "real" fix for that problem but running > > kill -HUP 1 > > before using ngc works for me. > > regards > > Hans > -- _______________________________________________ Initng mailing list [email protected] http://jw.dyndns.org/mailman/listinfo/initng
