issue.net

[Google Code Exporter]

What steps will reproduce the problem?
1. Add a SSH banner not null
2.
3.

What is the expected output? What do you see instead?
The error log display the banner, is this normal?


What version of the product are you using? On what operating system?
On Debian squeeze: 2.1.1-1

Please provide any additional information below.

Original issue reported on code.google.com by [e-mail] on 18 Jul 2011 at 1:40

[Google Code Exporter]

I'm afraid I don't understand.  Would you please provide more information?

Original comment by [e-mail] on 18 Jul 2011 at 2:56

• Added labels: ****
• Removed labels: ****

[Google Code Exporter]

[deleted comment]

[Google Code Exporter]

Hi,

Sorry for not being clear.

Here is the situation:
I have setup my servers with a banner SSH (Option Banner in sshd_config). I am 
trying to use pssh and when I use the option -e error_dir, in the error log the 
banner is showing in it; this means the error log size is not 0. So I wonder if 
it is possible to by pass this small inconvenient?

It is not a big deal just a question.


Regards,
JM

Original comment by [e-mail] on 18 Jul 2011 at 3:13

• Added labels: ****
• Removed labels: ****

[Google Code Exporter]

Unfortunately, pssh doesn't have any way of knowing what's part of the ssh 
banner and what isn't. All it can differentiate is whether ssh is writing to 
standard output or standard error. Is there an ssh option to omit the banner? 
If you're trying to get at the return code for each command (to determine 
whether or not there was an error), you can parse the output of pssh. Or 
perhaps we could consider adding an option to write all of the error codes to a 
file or directory.

Original comment by [e-mail] on 18 Jul 2011 at 4:03

• Added labels: ****
• Removed labels: ****

[Google Code Exporter]

Thx for answering :)

Original comment by [e-mail] on 18 Jul 2011 at 4:11

• Added labels: ****
• Removed labels: ****

[Google Code Exporter]

Issue #57 would make this less of a problem if you are not interested at all in 
stderr.

Original comment by [e-mail] on 2 Sep 2011 at 11:20

• Added labels: ****
• Removed labels: ****

[Google Code Exporter]

I've applied pablo.barbachano's patch for Issue #57, which lets you use 
--inline-stdout if you don't care about stderr. Does this address your 
concerns, or is there anything further that pssh could do?

Original comment by [e-mail] on 19 Jan 2012 at 11:42

• Added labels: ****
• Removed labels: ****

[Google Code Exporter]

I'm going to go ahead and close this issue for now, but feel free to reopen it 
if you feel that there is anything else that should be considered. Thanks for 
your participation with pssh.

Original comment by [e-mail] on 24 Jan 2012 at 6:29

• Changed state: Done
• Added labels: ****
• Removed labels: ****