Comment 6 for bug 1196828

On Mon, Jul 08, 2013 at 07:45:40AM -0000, John Reid wrote:
> I see this on that link you provided: "init can never have zombie
> children. From the wikipedia article: When a process loses its parent,
> init becomes its new parent. Init periodically executes the wait system
> call to reap any zombies with init as parent. One of init's
> responsibilities is reaping orphans and parentless zombies" So I think
> that means init is the new parent not the old one.

Clarification: When a process dies, it becomes a zombie until its parent reaps
(wait/waitpid) it. If its parent dies without reaping it, the process gets
reparented to init, which has pid 1, which is in turn supposed to reap it. If
init doesn't reap the process (due to a bug in init itself), then it remains a
zombie child of init. So it's not that init can never have zombie children. It's
that init *should* never have zombie children for extended periods, because it's
init's job to reap these zombie children.

> This is the output of "banshee --debug" but at the moment I do not have
> a zombie banshee process. When I do, I'll re-run with "--debug"
>
> [...]

Unfortunately, this isn't very helpful -- that's a normal Banshee log. I need
the one when Banshee refuses to start in order to tell what's going on.

--
Kind regards,
Loong Jin