From: Florian Weimer <fw@deneb.enyo.de>
To: Yuri Edward <yuri6037@yuristudio.net>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Issue with fcntl FD_CLOEXEC and execve
Date: Sun, 21 Jun 2020 21:57:18 +0200 [thread overview]
Message-ID: <87y2og5h0h.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <fadc7cda-a84b-33ed-e15a-8203673f9d61@yuristudio.net> (Yuri Edward's message of "Sat, 20 Jun 2020 21:18:27 +0200")
* Yuri Edward:
> https://github.com/BlockProject3D/Framework/blob/ProcessManagement/Base/src/Framework/System/Process.cpp
> > This is the main class that performs fork, pipe, read, write and
if (fcntl(commonfd[PIPE_WRITE], FD_CLOEXEC, 1) != 0)
That's not how fcntl works. You need to use F_GETFD and F_SETFD to
set the FD_CLOEXEC flag.
next prev parent reply other threads:[~2020-06-21 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 20:40 Issue with fcntl FD_CLOEXEC and execve postmaster
2020-06-20 6:53 ` Florian Weimer
2020-06-21 18:46 ` Yuri Edward
[not found] ` <fadc7cda-a84b-33ed-e15a-8203673f9d61@yuristudio.net>
2020-06-21 19:57 ` Florian Weimer [this message]
2020-06-22 17:09 ` Yuri Edward
-- strict thread matches above, loose matches on Subject: below --
2020-06-21 19:03 Yuri Edward
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=87y2og5h0h.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=linux-c-programming@vger.kernel.org \
--cc=yuri6037@yuristudio.net \
/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 NNTP newsgroup(s).