Date: Sat, 10 May 2003 06:39:36 -0300
From: Werner Almesberger <wa@almesberger.net>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: anyone ever implemented a reparent(pid) syscall?
Message-ID: <20030510063936.D13069@almesberger.net>
References: <3EBBF965.4060001@nortelnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3EBBF965.4060001@nortelnetworks.com>; from cfriesen@nortelnetworks.com on Fri, May 09, 2003 at 02:54:29PM -0400
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1278
Lines: 32

Chris Friesen wrote:
> I would like some way for the main one to restart, read the 
> list of pids out of a file that it conveniently stashed away,
[...]

And until it has done this, any child death will still only be seen
by init. So you either didn't have a problem with this in the first
place, or you can make sure your children don't die while their
parents are changing, or you've just designed yourself a race
condition.

A design where the parent simply doesn't die would be much better.

> Has anyone ever done this?

You could use ptrace to pretty much this effect. Of course, this
only works if the child processes don't already use ptrace for
some other purpose, and your parent now needs to respond whenever
a child gets a non-terminal signal (in addition to the terminal
ones).

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/