From: Rob Landley <landley@trommello.org>
To: Balbir Singh <balbir.singh@wipro.com>
Cc: Andrew Morton <akpm@zip.com.au>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: is reparent_to_init a good thing to do?
Date: Wed, 10 Oct 2001 18:13:45 -0400 [thread overview]
Message-ID: <01101018134508.11498@localhost.localdomain> (raw)
In-Reply-To: <3BC3118B.8050001@wipro.com> <3BC42E65.3060706@wipro.com> <3BC446E0.5020604@wipro.com>
In-Reply-To: <3BC446E0.5020604@wipro.com>
On Wednesday 10 October 2001 09:02, BALBIR SINGH wrote:
> Balbir Singh wrote:
> > Rob Landley wrote:
> >> Or long lived kernel threads from short lived login sessions.
...
> Ooh! sorry this is a wrong approach to send SIGCHLD to the previous parent.
> AFAIK, all shells send their children SIGHUP when the shell exits, but SSH
> may have some special security consideration in waiting for all children to
> exit, does anyone know?
>
> Balbir
The problem I mentioned above was the reason "reparent_to_init" was created
in the first place. Here it is in the archive:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0105.0/0045.html
I.E. already fixed...
Google could probably find Jimmy Hoffa given half a chance... (If we could
just figure out how to connect it up to maps.yahoo.com...)
Rob
next prev parent reply other threads:[~2001-10-11 2:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 15:02 is reparent_to_init a good thing to do? BALBIR SINGH
2001-10-09 16:13 ` Andrew Morton
2001-10-09 20:26 ` Rob Landley
2001-10-10 11:17 ` BALBIR SINGH
2001-10-10 13:02 ` BALBIR SINGH
2001-10-10 22:13 ` Rob Landley [this message]
[not found] ` <mailman.1002644159.30689.linux-kernel2news@redhat.com>
2001-10-09 18:46 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 14:38 Jesse Pollard
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=01101018134508.11498@localhost.localdomain \
--to=landley@trommello.org \
--cc=akpm@zip.com.au \
--cc=balbir.singh@wipro.com \
--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.