From: bugzilla-daemon@bugzilla.kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 214871] Man(3) system outdated
Date: Tue, 02 Nov 2021 09:58:19 +0000 [thread overview]
Message-ID: <bug-214871-11311-mVXKKSo1Zs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214871-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214871
--- Comment #3 from Alejandro Colomar (man-pages) (alx.manpages@gmail.com) ---
Hi Adhemerval, Michael,
On 11/1/21 13:06, zatrazz wrote:
> Hi Alejandro,
>
> Indeed we changed glibc to use posix_spawn on system and popen on 2.29
> since
> to use posix_spawn (which uses clone (CLONE_VFORK | CLONE_VM)). It plays
> way better with Linux memory subsystem than fork() + exec() specially
> when such
> calls are used with process with large RSS.
I applied the following patch. I'll close the bug.
Thanks,
Alex
---
system.3: It doesn't call fork anymore
Reported-by: Michael Kearney <mikekearney85@hotmail.com>
Cc: Adhemerval Zanella <zatrazz@gmail.com>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
diff --git a/man3/system.3 b/man3/system.3
index 880fe93c6..bde45ed82 100644
--- a/man3/system.3
+++ b/man3/system.3
@@ -40,9 +40,9 @@ system \- execute a shell command
.SH DESCRIPTION
The
.BR system ()
-library function uses
+library function behaves as if it used
.BR fork (2)
-to create a child process that executes the shell command specified in
+to create a child process that executed the shell command specified in
.I command
using
.BR execl (3)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-11-02 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 20:37 [Bug 214871] New: Man(3) system outdated bugzilla-daemon
2021-10-30 11:56 ` [Bug 214871] " bugzilla-daemon
2021-11-01 12:06 ` bugzilla-daemon
2021-11-02 9:58 ` bugzilla-daemon [this message]
2021-11-02 9:58 ` bugzilla-daemon
2021-11-02 11:37 ` bugzilla-daemon
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=bug-214871-11311-mVXKKSo1Zs@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-man@vger.kernel.org \
/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