Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with buffer
Search options not deleted
user 47947
This tag is for questions about kernel buffer caches, including pipe buffers. These are used to store the recently accessed files and/or frequently accessed files.
14
votes
1
answer
1k
views
“Leaky” pipes in linux
If I wanted to avoid this, I could be tempted to use a bigger pipe (or, more simply, buffer(1)) like so:
$ a | buffer | b
This would simply buy me more time, but in the end a would eventually stop. … To sum it up I would love to have something like a bounded, leaky buffer:
$ a | leakybuffer | b
I could probably implement it quite easily in any language, I was just wondering if there's something " …
- 251