21.11.2011 17:20, Denys Vlasenko пишет: > On Sun, Nov 20, 2011 at 9:22 PM, Alexander Varnin <[email protected]> wrote: >> I also figured out, that the only entry about init in logs is >> >> / # cat /var/log/messages | grep >> starting >> >> Jan 1 00:00:02 (none) daemon.info init: starting pid 53, tty >> '/dev/console': '/bin/sh' >> >> So this action gets read from inittab and executed. But others - not. > How do you know it if you /dev/null'ed stdout and stderr > of your sysinit actions? First i've tried to change null to console in inittab with no effect. And second i've checked the effect of commands - hostname doesn't get set, and fs doesn't get mounted. That all i checked in log, that was attached to my first message.
> >> And nothing even gets printed in logs, though init.c busybox file >> contains much calls to message(L_LOG,...) function. > L_LOG messages won't be logged to system log until syslogd > is started. Apparently it is not started soon enough (or ever) > to capture them. > > I also noticed that you don't reply to my suggestions. Sorry for that. /dev/console is in place. About this message message(L_CONSOLE | L_LOG, "init started: %s", bb_banner); I can't see it also. But I can see message in /var/log/messages, that is written from "run" function from init.c. _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
