Re: system and popen fail in case of big application

[Sergey Melnikov <melnikov.sergey.v@gmail.com>]

Mark,

Thank you for your guidance. I'll write man for vfork and prepare a patch.

Regarding FSF. I had signed FSF during my work at Intel (I worked on
gcc for android x86). Should I sign this one more time as an
individual contributor (I don't work at Intel anymore)?

--Sergey
On Mon, Sep 10, 2018 at 1:47 AM Zack Weinberg <zackw@panix.com> wrote:
>
> On Sun, Sep 9, 2018 at 6:44 PM Zack Weinberg <zackw@panix.com> wrote:
> > On Sun, Sep 9, 2018 at 6:16 PM Sergey Melnikov
> > <melnikov.sergey.v@gmail.com> wrote:
> > > If so, I may implement and contribute this to glibc.
> >
> > What would be worthwhile is to change popen and system so that they
> > internally use *vfork*, on systems where vfork is not the same as fork.
>
> I meant to say explicitly that if you write patches that do this, we
> will definitely consider them for inclusion.  However, you're going to
> need to file a copyright assignment with the FSF.  This can be slow,
> so you should get the process started immediately.  See
> https://sourceware.org/glibc/wiki/Contribution%20checklist#FSF_copyright_Assignment
> .
>
> zw



-- 

--Sergey