Re^2: Capturing bash output without displaying STOUT in terminal

Replies are listed 'Best First'.
Re^3: Capturing bash output without displaying STOUT in terminal by dasgar (Priest) on Sep 08, 2016 at 16:29 UTC
Based on your response to my post as well as stevieb's initial post, I'd agree with stevieb that it looks like the command that you're running is sending the response to STDERR. As stevieb has pointed out, his suggestion of using backticks will only let you capture STDOUT. Capture::Tiny can capture both STDOUT and STDERR (and exit code) for system commands.	[reply]
Re^4: Capturing bash output without displaying STOUT in terminal by bart (Canon) on Sep 08, 2016 at 19:17 UTC
Or, you can append `2>&1` to the command line, allowing STDERR to be captured through STDOUT. Only recommended if the normal STDOUT is empty.	[reply] [d/l]
Re^3: Capturing bash output without displaying STOUT in terminal by ikegami (Patriarch) on Sep 08, 2016 at 21:36 UTC
Some programs (e.g `ssh` when asking for a password) write directly to the terminal, not STDOUT. `$ ssh ikegami@209.197.123.153 2>&1 >/dev/null ikegami@209.197.123.153's password:` [download] You have to create pseudo-tty's (as Expect does) in that case. IPC::Run supports capturing STDOUT and STDERR separately, and easily. It even supports pseudo-tty creation if you need them.	[reply] [d/l] [select]