Problem with PPID
Marc Blumentritt
marc.blumentritt at arcor.de
Mon Nov 5 08:29:20 PST 2007
Denys Vlasenko schrieb:
> On Sunday 04 November 2007 17:54, Marc Blumentritt wrote:
>> Denys Vlasenko schrieb:
>>> On Sunday 04 November 2007 12:07, Marc Blumentritt wrote:
>>>
>>> mount -t proc proc /proc
>>> ps -a > /ps_init_data
>> Now I have these results:
>> root at mediamachine $ cat /ps_init_data
>> PID USER COMMAND
>> 1 root init
[...]
>> 824 root [kpsmoused]
>> 833 root init
>> 834 root /bin/sh /sbin/rc.init
>> 836 root ps -A
>>
>> Is this the expected result, that init starts first a child of itself,
>> which then starts my init script rc.init?
>
> Apparently yes. It happens in init/init.c, in this function:
>
> static pid_t run(const struct init_action *a)
>
> I think it should be either explained in detail in the comments,
> or simplified.
If you mean simplified by not creating first a child of init, I'm right
for it, since then system init scripts can check in a simple way, if
they are started by init or not.
Anyway, I know now where this PPID comes from, so thanks for your help.
Regards,
Marc
More information about the busybox
mailing list