[Michael] > I have some questions: > > (1) What does the '2' in the 'init [2]' entry of the ps output mean ?
It mean the current runlevel is 2. > (2) Why does udev launch 100 processes ? Is this normal ?? No idea, but probably. I have been told that udev spawn ~1000 modprobe processes during boot, so 100 do not surprise me. > (3) What does SELINUX_INIT=YES (in the process environment) mean ? > Package SeLinux is not installed here! Not sure, but know the sysvinit package is prepared for SELinux. Perhaps it is a signal that this is the case? > (4) When the script had another desing, before, i could see 63 * > console-kit at boot time. I guess the processes are launched and > terminated again so quickly that the 'ps' snapshot is variable. No idea what console-kit is doing during boot. > I can see some essential services FAIL (syslog, cron and > xientd). But apparently they are just running later. I suspect it's > because some redundant init process tries to start them twice. I agree that this sound likely. > However, i can not find these FAIL messages in any log in /var/log > (for example, not with grep -r FAIL *, nor when i grep for the > service name). Did you enable bootlogd? Edit /etc/default/bootlogd. But as it is stopped at the end of runlevel 2, only the first invocation of runlevel 2 would be recorded. Can you provide the content of /etc/inittab? Or just the output of 'grep -v '#' /etc/inittab' to ignore comments. If there is nothing to be found there, I have no idea what is wrong. _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
