Edit - Unix & Linux Stack Exchange

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.

POSIX leaves it unspecified what write(1, "", 0) does on a pipe and on Linux, I find it doesn't do anything even on a broken pipe.

Stéphane Chazelas
– Stéphane Chazelas

2023-02-24 18:35:09 +00:00
Commented Feb 24, 2023 at 18:35
@StéphaneChazelas, yeh, the man page I was reading says "If all file descriptors referring to the read end of a pipe have been closed, then a write(2) will cause a SIGPIPE signal to be generated for the calling process." though I'm not surprised a zero-byte write would be different. But as mentioned, it doesn't matter here.

ilkkachu
– ilkkachu

2023-02-25 10:01:36 +00:00
Commented Feb 25, 2023 at 10:01

Add a comment |

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

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>

formatting help »
answering help »