Explore >> Select a destination
|
You are here 
|
jameshfisher.com | ||
| | | | |
thorstenball.com
|
|
| | | | | ||
| | | | |
rickardlindberg.me
|
|
| | | | | I thought I knew how Bash redirects worked. If I wanted to redirect the output of a command to a file, I'd type this: program > /tmp/log.txt If I wanted to pipe both stdout and stderr to a text editor for further processing, I'd type this: program 2>&1 | vim - I knew that 2>&1 meant redirect stderr to stdout making it appear on stdout as well. I knew certain patterns for certain situations. | |
| | | | |
blog.nelhage.com
|
|
| | | | | reptyr (announced recently on this blog) takes a process that is currently running in one terminal, and transplants it to a new terminal. reptyr comes from a proud family of similar hacks, and works in the same basic way: We use ptrace(2) to attach to a target process and force it to execute code of our own choosing, in order to open the new terminal, and dup2(2) it over stdout and stderr. | |
| | | | |
blog.yoshuawuyts.com
|
|
| | | |||
