Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Redirect redir errors to /dev/null #51
This change also completely masks errors like redir package not being installed. Instead port forwarding fails, while "vagrant reload" output looks perfect. (Just got bitten by this).
Also if redir isn't able to bind to a port, then it'll print out
Is there a better way to handle this? At least, is it possible to trap errors from launching redir, currently done using Kernel.spawn?
For future Googlers: At first, I mistook my problem to be the same as the one mentioned in this tutorial:
For my notes: I was able to reproduce the
bash$ screen screen1$ sudo redir --laddr=127.0.0.1 --lport=9090 --cport=12345 --caddr=10.0.3.226 # nothing listening on 12345 screen2$ curl localhost:9090 # this makes redir spit out 'target: connect: Connection refused' in screen1
@dergachev so I gave this some thought today and I'm leaning towards keeping the redirect if we are not able to think of other issues because:
what might be a good idea is to allow redirecting