Re: popen/pclose problem in Linux 2.2.x with vfork/glibc 2.1

[Cristian Gafton <gafton@redhat.com>]

On 29 Mar 1999, Ulrich Drepper wrote:

> > Thanks for all replies.  I do think we have to use fork instead of
> > vfork for popen in glibc since the code changes some globals and calls
> > dup2 and close:
> 
> I don't think this is necessary.  The changes to global variables and
> functions calls should not effect the main process.  Before we make
> any change it should be clear it's necessary.  Using vfork has its
> advantages.

Well, the fact that changing from vfork to fork makes some programs that
are using nothing more than popen() calls work again and not
randomly segfault speak for the fact that somthing is rotten when using
vfork.

Add my "vote" for changing popen implementation to use fork instead of
vfork.

Cristian
--
----------------------------------------------------------------------
Cristian Gafton   --   gafton@redhat.com   --   Red Hat Software, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 UNIX is user friendly. It's just selective about who its friends are.