Re: init + orphaned processes

From: Paul Pluzhnikov (ppluzhnikov-nsp_at_charter.net)
Date: 03/29/04 

Date: 28 Mar 2004 22:53:31 -0800

Matty <mattyml@bellsouth.net> writes:

> Does anyone know when init will
> terminate processes it inherits and reclaim
> the resources?

Init never does *that*.

What it does do is wait(2) for *already* terminated processes
(aka zombie processes).

If you actually do have zombie processes, and they are not cleaned
up by init, then your init process is likely stuck. One reason this
could happen is given here:

  1.153 Why does init not reap its zombie child processes?
  http://www.faqs.org/faqs/aix-faq/part1/section-61.html

If you are not on AIX, pray tell what OS you are on, and what the
'ps -ef' output for "stuck" processes looks like.

> I am parsing through Advanced
> Programming in the UNIX Environment in an attempt to
> find an answer.

Why not ask the application vendor how the app is supposed to
be terminated?

Cheers, 

-- 
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.

Relevant Pages

  • Re: init + orphaned processes
    ... The PPID is 1, which should allow init ... >> terminate processes it inherits and reclaim ... > This is called a zombie process and is the result of the parent process ... That is not a zombie. ...
    (comp.unix.admin)
  • Re: coredump
    ... Q. Why should I not top-post? ... _init() ## this init is probably in your library ... Apparently your library has a global object, ... In order to understand recursion you must first understand recursion. ...
    (comp.unix.programmer)
  • Re: Developing application for linux
    ... With an editor? ... Assuming your target is configured to run "init", ... In order to understand recursion you must first understand recursion. ...
    (comp.os.linux.embedded)