This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug nptl/378] posix_spawn implementation, use vfork/execve rather than fork/execve for NPTL Linux.
- From: "dennis at mds dot rmit dot edu dot au" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 13 Sep 2004 07:57:13 -0000
- Subject: [Bug nptl/378] posix_spawn implementation, use vfork/execve rather than fork/execve for NPTL Linux.
- References: <20040910004801.378.dennis@mds.rmit.edu.au>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- Additional Comments From dennis at mds dot rmit dot edu dot au 2004-09-13 07:57 -------
Well spotted.
I guess application developers will need to know how
each posix_spawn implementation deals with atfork handlers.
The Solaris 10 man page indicates clearly what they do.
If a change does occur in the NPTL glibc posix_spawn (fingers
crossed), again the man will need to state clearly what happens
in each situation (fork/exec path and possible vfork/exec path).
It does appear that a vfork-path based posix_spawn which
does not run atfork handlers will be safe, fast and
standards complient.
--
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.