When you use a TTY, all of the output channels are merged, so you no longer get separate stderr/stdout:
https://stackoverflow.com/questions/16838624/why-does-openssh-requesttty-cause-stderr-redirected-to-stdout/16839544#16839544
I think this means that we have a decision to make between:
- separate stderr/stdout channels
- interactive stdin
Solutions are to:
- modify the command to add
2> /dev/null, essentially discarding all stdout, or
- update the code to not use stdout to local file, but instead support downloading a file on command completion
- Use
sed -i '1d' *.xml to remove the first line from the output files (assuming the hostgroup warning on the first line is the only issue)
When you use a TTY, all of the output channels are merged, so you no longer get separate
stderr/stdout:https://stackoverflow.com/questions/16838624/why-does-openssh-requesttty-cause-stderr-redirected-to-stdout/16839544#16839544
I think this means that we have a decision to make between:
Solutions are to:
2> /dev/null, essentially discarding all stdout, orsed -i '1d' *.xmlto remove the first line from the output files (assuming the hostgroup warning on the first line is the only issue)