From: Zack Weinberg <zackw@panix.com>
To: melnikov.sergey.v@gmail.com
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: system and popen fail in case of big application
Date: Sun, 09 Sep 2018 22:47:00 -0000 [thread overview]
Message-ID: <CAKCAbMhDcW2zjB1sh1OU1v_4Gf-hTpsHHFWj8Bwmsg7sUtHTPg@mail.gmail.com> (raw)
In-Reply-To: <CAKCAbMgVg8RyKeEZi40EL2CG=V859RYS541YGMHS4dyTp_mVWg@mail.gmail.com>
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
next prev parent reply other threads:[~2018-09-09 22:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 22:16 Sergey Melnikov
2018-09-09 22:44 ` Zack Weinberg
2018-09-09 22:47 ` Zack Weinberg [this message]
2018-09-09 23:27 ` Sergey Melnikov
2018-09-09 23:49 ` Zack Weinberg
2018-09-10 2:50 ` Martin Buchholz
2018-09-10 15:38 ` Joseph Myers
2018-09-10 15:42 ` Zack Weinberg
2018-09-10 15:43 ` Joseph Myers
[not found] ` <CA+kOe0_1k_PbJ-pjHznP4AmTJUgziAdT+4vCcCRSb7GGdvbv7Q@mail.gmail.com>
2018-09-10 15:59 ` Zack Weinberg
2018-09-10 16:55 ` Martin Buchholz
2018-09-11 20:16 ` Adhemerval Zanella
2018-09-12 16:30 ` Zack Weinberg
2018-09-12 19:46 ` Martin Buchholz
2018-09-13 1:27 ` Adhemerval Zanella
2018-09-13 6:31 ` Andreas Schwab
2018-09-13 12:30 ` Adhemerval Zanella
2018-09-18 1:18 ` Martin Buchholz
2018-09-18 1:59 ` Adhemerval Zanella
2018-09-18 2:18 ` Martin Buchholz
2018-09-18 4:31 ` Rich Felker
2018-09-12 23:08 ` Adhemerval Zanella
2018-09-13 12:11 ` Szabolcs Nagy
2018-09-14 18:42 ` Zack Weinberg
2018-09-17 10:32 ` Szabolcs Nagy
2018-09-17 18:27 ` Adhemerval Zanella
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=CAKCAbMhDcW2zjB1sh1OU1v_4Gf-hTpsHHFWj8Bwmsg7sUtHTPg@mail.gmail.com \
--to=zackw@panix.com \
--cc=libc-alpha@sourceware.org \
--cc=melnikov.sergey.v@gmail.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).