From: Scott James Remnant <scott@canonical.com>
To: Lennart Poettering <lennart@poettering.net>
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [PATCH/RFC] exit: PR_SET_ANCHOR for marking processes as reapers for child processes
Date: Thu, 04 Jun 2009 12:50:55 +0100 [thread overview]
Message-ID: <1244116255.4120.33.camel@quest> (raw)
In-Reply-To: <20090528204729.GA28564@omega>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
On Thu, 2009-05-28 at 22:47 +0200, Lennart Poettering wrote:
> Right now, if a process dies all its children are reparented to init.
> This logic has good uses, i.e. for double forking when
> daemonizing. However it also allows child processes to "escape" their
> parents, which is a problem for software like session managers (such
> as gnome-session) or other process supervisors [1].
>
As we discussed on IRC, another option is for the session
manager/process supervisor to use the proc connector to receive messages
about fork() and exit() - then it doesn't need to receive SIGCHLD, so it
doesn't matter where the process reparents to.
OTOH, this patch would make the process trees much prettier <g>
Scott
--
Scott James Remnant
scott@canonical.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-06-04 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 20:47 [PATCH/RFC] exit: PR_SET_ANCHOR for marking processes as reapers for child processes Lennart Poettering
2009-06-04 11:50 ` Scott James Remnant [this message]
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=1244116255.4120.33.camel@quest \
--to=scott@canonical.com \
--cc=kay.sievers@vrfy.org \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
/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.