| bio | website | |
|---|---|---|
| location | Sydney, Australia | |
| age | 24 | |
| visits | member for | 7 months |
| seen | May 19 at 12:57 | |
| stats | profile views | 10 |
|
Apr 15 |
comment |
How to duplicate a stream and process both parts in a streaming way? I discovered this just this afternoon, by coincidence. Thanks! |
|
Apr 15 |
accepted | How to duplicate a stream and process both parts in a streaming way? |
|
Apr 15 |
comment |
Can't process stdout with pipe as it comes Great trick, but stdio buffering exists for a good reason, and it's lame that utilities which mess with stuff like isatty() force you to do this. |
|
Apr 15 |
comment |
Can't process stdout with pipe as it comes Yo may need to put the entire command in quotes. Gets tricky with such a complex command. Try putting your entire call to tshark in a shell script, and then doing script -c myscript.sh. |
|
Apr 15 |
answered | Can't process stdout with pipe as it comes |
|
Apr 14 |
comment |
local email storage syncing to imap - mutt-friendly Thanks. I found isync, now named absync. It's working well! |
|
Apr 14 |
comment |
How to duplicate a stream and process both parts in a streaming way? If performance is crucial and the process you want to run is fairly trivial, you could reimplement (for example) a version of wc that prints its result to stderr, and ensures that every byte from stdin comes out of its stdout. Beware, though, that an architecturally more 'efficient' implementation may be slower anyway as coreutils and sed/awk are heavily optimised for many tasks. |
|
Apr 14 |
asked | How to duplicate a stream and process both parts in a streaming way? |
|
Apr 14 |
answered | How to duplicate a stream and process both parts in a streaming way? |
|
Apr 14 |
asked | local email storage syncing to imap - mutt-friendly |
|
Mar 24 |
comment |
Races when piping two commands to a named pipe From the point of view of simplicity, there is nothing broken about the read side. In practise I will connect this pipe to the stdin of a process that does some stream processing and writes stuff out; EOF on STDIN is EOF on STDIN. |
|
Mar 24 |
comment |
Races when piping two commands to a named pipe I understand this; the issue that I have is that cat is seeing EOF on the pipe in the first place. I need to control the behaviour so that i can redirect the output of N processes to the write end of the pipe before it's closed (ie before the reader, in this case cat, sees EOF). |
|
Mar 24 |
asked | Races when piping two commands to a named pipe |
|
Feb 20 |
awarded | Scholar |
|
Feb 20 |
accepted | Managing the output streams of many subprocesses with deadlocks |
|
Feb 20 |
comment |
Managing the output streams of many subprocesses with deadlocks Thanks, a select() loop on stderr is actually perfect for what I'm trying to do - as long as I make sure I don't close stderr in the child processes before they exit. |
|
Feb 9 |
awarded | Commentator |
|
Feb 9 |
comment |
Managing the output streams of many subprocesses with deadlocks I'm looking at the retcode to decide whether it failed, but I need the stderr to get the log output and send it off or propagate the error reporting. |
|
Feb 9 |
asked | Managing the output streams of many subprocesses with deadlocks |
|
Dec 27 |
answered | Can't boot live USB of Linux Mint DE on my UEFI PC |