lkml.org 
[lkml]   [2003]   [May]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: anyone ever implemented a reparent(pid) syscall?
Werner Almesberger wrote:
> 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.

Sure. So the monitorer starts up, attempts to watch a pid, gets an error saying
that it doesn't exist, and handles it.

In the particular case that I'm planning for, the processes in question are
long-running ones which should never die except for upgrades (which could be
designed for).

The general case would be trickier.

Chris


--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:35    [W:0.040 / U:1.248 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site