Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16242
| From | Ángel <angel@16bits.net> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Unbuffered pipes: cases to be supported |
| Date | 2020-04-25 17:26 +0200 |
| Message-ID | <mailman.1218.1587828421.3066.bug-bash@gnu.org> (permalink) |
| References | <878silvimy.fsf@hobgoblin.ariadne.com> <1587828412.1138.2.camel@16bits.net> |
On 2020-04-23 at 20:20 -0400, Dale R. Worley wrote: > The cases I've found where bash allocates a pipe, and thus an unbuffered > pipe may be wanted, are: What are you trying to solve? How do you expect those "Unbuffered pipes" to be implemented? I don't think there is any buffering going on in the pipes itself. The problem is likely to be at the program *writing* to the pipe. Which is out of the scope of bash itself. You may want to run them through stdbuf Best regards
Back to gnu.bash.bug | Previous | Next | Find similar
Re: Unbuffered pipes: cases to be supported Ángel <angel@16bits.net> - 2020-04-25 17:26 +0200
csiph-web