From: Florian Weimer <fw@deneb.enyo.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Roland McGrath <roland@redhat.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Ulrich Drepper <drepper@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] bug in setpgid()? process groups and thread groups
Date: Sun, 03 Aug 2003 09:22:14 +0200 [thread overview]
Message-ID: <8765lfxl21.fsf@deneb.enyo.de> (raw)
In-Reply-To: <1059857483.20306.6.camel@dhcp22.swansea.linux.org.uk> (Alan Cox's message of "02 Aug 2003 21:51:24 +0100")
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> #1 Lots of non posix afflicted intelligent programmers use the per
> thread uid stuff in daemons. Its really really useful
It doesn't work reliably because the threading implementation might
have to send signals which the current combination of credentials does
not allow.
IMHO, POSIX is wrong to favor process attributes so strongly. It
wouldn't be a problem if there were other ways to pass these implicit
parameters (such as thread-specific attributes, or, even better,
syscall arguments). But often there isn't.
next prev parent reply other threads:[~2003-08-03 7:22 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 [this message]
2003-08-03 21:00 ` Alan Cox
2003-08-03 4:15 ` Jeremy Fitzhardinge
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=8765lfxl21.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=drepper@redhat.com \
--cc=jeremy@goop.org \
--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