On Tue, Aug 09, 2011 at 05:47:09PM -0700, Linda Walsh wrote:
Bob Proulx wrote:
This may be a good point to mention this reference:
http://www.pixelbeat.org/programming/stdio_buffering/
Does it only work with gnu programs? I.e. how would they know to
not buffer
Sounds like
Greg Wooledge wrote:
Linda Walsh wrote:
Bob Proulx wrote:
This may be a good point to mention this reference:
http://www.pixelbeat.org/programming/stdio_buffering/
Does it only work with gnu programs? I.e. how would they know to
not buffer
Sounds like the GNU
On Wed, Aug 10, 2011 at 10:07:20AM -0600, Bob Proulx wrote:
The unbuffer expect script sets up a tty around the called program so
that instead of a pipe the program detects a tty.
The stdbuf utility works by setting up an LD_PRELOAD library
libstdbuf.so that replaces the libc calls and
On 8/3/11 4:11 PM, Linda Walsh wrote:
I've searched for coproc usage examples on the web, but there aren't
many, and the few I found, while working for their test case, didn't
fully replicate my setup, so it didn't work.
Ideas?
What am I doing wrong?
You're probably running into
Chet Ramey wrote:
What am I doing wrong?
You're probably running into grep (and sort, and sed) buffering its
output. I haven't been able to figure out a way past that.
Chet
---
I did think of that...but I thought when the foreground
process closes 'input', then all of the chained
Linda Walsh wrote:
I did think of that...but I thought when the foreground
process closes 'input', then all of the chained utils should see 'eof', and
should then flush their output...at least that was my belief in how they
should be working...(sigh)...
---
Um...that got me to
Chet Ramey wrote:
Linda Walsh wrote:
Ideas?
You're probably running into grep (and sort, and sed) buffering its
output. I haven't been able to figure out a way past that.
This may be a good point to mention this reference:
http://www.pixelbeat.org/programming/stdio_buffering/
And the
Bob Proulx wrote:
Chet Ramey wrote:
Linda Walsh wrote:
Ideas?
You're probably running into grep (and sort, and sed) buffering its
output. I haven't been able to figure out a way past that.
This may be a good point to mention this reference:
On 8/9/11 8:19 PM, Linda Walsh wrote:
Linda Walsh wrote:
I did think of that...but I thought when the foreground
process closes 'input', then all of the chained utils should see 'eof', and
should then flush their output...at least that was my belief in how they
should be
I'm trying to make first use of a coproc and having difficulties.
Multiple versions I've tried (so exact details like how to do
redirection in statement 10, have been varied in many non-working ways!
But showing the last version:
awk would be much better suited for this task.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something completely different.
I could do the whole thing in perl as well.
Part of my reluctance to do that, is I wanted to learn why coproc
wasn't working, and how to make it work.
If I only use 'old skills', how will I learn anything new?
Andreas Schwab wrote:
awk would be much better suited for this task.
Andreas.
12 matches
Mail list logo