public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roland at gnu dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/378] posix_spawn implementation, use vfork/execve rather than fork/execve for NPTL Linux.
Date: Sun, 12 Sep 2004 22:54:00 -0000 [thread overview]
Message-ID: <20040912225451.24725.qmail@sourceware.org> (raw)
In-Reply-To: <20040910004801.378.dennis@mds.rmit.edu.au>
------- Additional Comments From roland at gnu dot org 2004-09-12 22:54 -------
I don't think the option should be about the implementation detail.
If ought to be POSIX_SPAWN_NO_ATFORK, meaning that atfork handlers do not get run.
In practice, that means calling vfork instead of fork. But the name and meaning
of the switch should be about the application experience, not the system's
implementation.
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=378
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2004-09-12 22:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 0:48 [Bug nptl/378] New: " dennis at mds dot rmit dot edu dot au
2004-09-12 5:56 ` [Bug nptl/378] " drepper at redhat dot com
2004-09-12 18:06 ` drepper at redhat dot com
2004-09-12 22:54 ` roland at gnu dot org [this message]
2004-09-13 1:22 ` drepper at redhat dot com
2004-09-13 3:10 ` roland at gnu dot org
2004-09-13 4:18 ` dennis at mds dot rmit dot edu dot au
2004-09-13 6:35 ` jakub at redhat dot com
2004-09-13 7:46 ` roland at gnu dot org
2004-09-13 7:57 ` dennis at mds dot rmit dot edu dot au
2004-09-13 8:06 ` dennis at mds dot rmit dot edu dot au
2005-04-06 22:03 ` chris dot quenelle at sun dot com
[not found] <bug-378-131@http.sourceware.org/bugzilla/>
2014-06-13 10:43 ` fweimer at redhat dot com
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=20040912225451.24725.qmail@sourceware.org \
--to=sourceware-bugzilla@sources.redhat.com \
--cc=glibc-bugs@sources.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 read-only IMAP folder(s) and NNTP newsgroup(s).