You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- Note that neither process 2 nor process 3 will be able to signal EOF to the other while process 1 has the file descriptors open. Process 1 must close both descriptors so the write process will get a SIGPIPE signal if it writes to the pipe but the reader has terminated or closed the pipe. Similarly, the reader process will not be notified that the writer process has terminated or closed the pipe. That's because in each case, process 1 could write or read data because it has open file descriptors referring to the pipe file descriptors.Jonathan Leffler– Jonathan Leffler2023-10-30 22:22:45 +00:00Commented Oct 30, 2023 at 22:22
- @JonathanLeffler: process 1 might wait for the end of process 2 and close the write end of the pipe immediately, even when process 3 is running (and vice versa). Gives the same effect as when process 1 just passes ownership of the file descriptors directly to proc 2 and 3 and lets them close the files directly.Doc Brown– Doc Brown2023-10-30 22:32:30 +00:00Commented Oct 30, 2023 at 22:32
- And unless the sub-processes have a mechanism other than encountering EOF on read or failing to write, they will not terminate tidily. In particular, the writer might block waiting for a process to read data from the pipe, but no process is trying to read the pipe. Similarly, the reader might be blocked trying to read from an empty pipe that no process is going to write to. Care is required!Jonathan Leffler– Jonathan Leffler2023-10-30 22:38:17 +00:00Commented Oct 30, 2023 at 22:38
- @JonathanLeffler: sure, but what do you think does this say about who should close the files?Doc Brown– Doc Brown2023-10-30 23:03:03 +00:00Commented Oct 30, 2023 at 23:03
- It says process 1 should close both ends of the pipe before waiting on either process 2 or process 3. Otherwise, it will most likely be waiting “forever”.Jonathan Leffler– Jonathan Leffler2023-10-30 23:33:43 +00:00Commented Oct 30, 2023 at 23:33
| Show 3 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-c