Re: capture STDOUT when some jerk opened STDOUT to /dev/tty

I'm not allowed to touch the script. That's completely forbidden.

Make your own local copy of the script, tweak and run that. The original is untouched.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re: capture STDOUT when some jerk opened STDOUT to /dev/tty

Replies are listed 'Best First'.
Re^2: capture STDOUT when some jerk opened STDOUT to /dev/tty by Tommy (Chaplain) on Jan 07, 2013 at 21:41 UTC
It communicates with a remote server to get the data it must process, and the remote server won't communicate with the script unless it has the right crypto hash... I decided the rabbit hole was getting too deep, and I wrote my own version in 1 line of shell code (a very long line with lots of pipes and regexen). sigh... Sometimes to win, you just have to know when you're beaten. Tommy "Perl follows the principle of least astonishment"	[reply]

Replies are listed 'Best First'.

Re^2: capture STDOUT when some jerk opened STDOUT to /dev/tty
by Tommy (Chaplain) on Jan 07, 2013 at 21:41 UTC

It communicates with a remote server to get the data it must process, and the remote server won't communicate with the script unless it has the right crypto hash...

I decided the rabbit hole was getting too deep, and I wrote my own version in 1 line of shell code (a very long line with lots of pipes and regexen). *sigh*... Sometimes to win, you just have to know when you're beaten.

Tommy
"Perl follows the principle of least astonishment"

[reply]