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.

Required fields*

Rev

In addition to named pipes, you could also consider unix domain sockets.

Andy Dalton
– Andy Dalton

2016-04-12 14:57:42 +00:00
Commented Apr 12, 2016 at 14:57
Named pipes are problematic when you have multiple simultaneous readers; you'll frequently get a reader that gets part of the data. Sockets are a problem when you have no control over the reader; you can't open a socket the same way you can a file or pipe.

Chris Cogdon
– Chris Cogdon

2017-12-05 17:26:49 +00:00
Commented Dec 5, 2017 at 17:26

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 »