From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Werner Almesberger <wa@almesberger.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: anyone ever implemented a reparent(pid) syscall?
Date: Sun, 11 May 2003 23:23:04 -0400 [thread overview]
Message-ID: <3EBF1398.9090704@nortelnetworks.com> (raw)
In-Reply-To: 20030510063936.D13069@almesberger.net
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
next prev parent reply other threads:[~2003-05-12 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 18:54 anyone ever implemented a reparent(pid) syscall? Chris Friesen
2003-05-10 9:39 ` Werner Almesberger
2003-05-12 3:23 ` Chris Friesen [this message]
2003-05-12 7:33 ` Werner Almesberger
2003-05-12 14:03 ` Chris Friesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EBF1398.9090704@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wa@almesberger.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.