[BusyBox] init problem with init.c version 1.164 from CVS

Vladimir N. Oleynik dzo at simtreas.ru
Wed Jul 24 10:15:05 UTC 2002


Cajus,
 
> I have some problems with the latest version of the init.c from the stable
> CVS archive.
> I was using the version from busybox 0.60.3 stable before.
> In the inittab I start a script with the sysinit-action and another with
> the once-action.
> This scripts itself execute some applications, which continue runnig in
> background.
> Some of this applications print on their stdout (with printf).
> This output appears on the console.
> I can see the first few lines with output, then the output stops.
> It looks like the problem results in the exit of the init action.
> Some of my application exited completely (not only their output).
> I found out, that they got a SIGHUP, which made them quit.
> I solved this with a signal handler.

IHMO and should work.
If process start as background, you must drop controlling tty
or ignore sighup and rreopen stdin/stdout/stderr to /dev/null.
I can`t understand yours problems.

> Is the stdout of this init-childs closed when the init action exits?
> This problem does not occur with init.c from busybox 0.60.3 stable.


--w
vodz



More information about the busybox mailing list