From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Roland McGrath <roland@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] bug in setpgid()? process groups and thread groups
Date: 02 Aug 2003 21:15:13 -0700 [thread overview]
Message-ID: <1059884113.20511.7.camel@ixodes.goop.org> (raw)
In-Reply-To: <200308021908.h72J82x10422@magilla.sf.frob.com>
On Sat, 2003-08-02 at 12:08, Roland McGrath wrote:
> In the case of pgrp, you can
> ignore SIGTTIN/SIGTTOU and progress to some degree at user level. In the
> case of uids/gids, you can change every thread individually.)
In my case I'm getting read() returning EIO when it tries to read from
the terminal, because the thread pgid doesn't equal the terminal
foreground pgid. I could solve this problem if either setpgid sets the
pgid in all threads in the thread group, or if I could run setpgid in
all threads for myself (I would prefer the latter just because it is a
bit more flexible). The current situation is just annoyingly broken
because there's no user-space way to fix it.
J
next prev parent reply other threads:[~2003-08-03 4:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 7:57 [PATCH] bug in setpgid()? process groups and thread groups Jeremy Fitzhardinge
2003-08-02 8:20 ` Ulrich Drepper
2003-08-02 8:50 ` Jeremy Fitzhardinge
2003-08-02 19:08 ` Roland McGrath
2003-08-02 20:30 ` Nicholas Miell
2003-08-02 20:51 ` Alan Cox
2003-08-03 7:22 ` Florian Weimer
2003-08-03 21:00 ` Alan Cox
2003-08-03 4:15 ` Jeremy Fitzhardinge [this message]
2003-08-02 18:39 ` William Lee Irwin III
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=1059884113.20511.7.camel@ixodes.goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).