I don't want to get involved in the shouting match here, but I did want to say I always use Google and search the web (before posting any questions) since 90% of questions asked are already answered somewhere else, although I didn't find anything pertaining to my exact situation.
I also knew that salva frequents here (and thankfully he helped me correct my mistake, even though it wasn't an Net::OpenSSH error) | [reply] |
Oh, my stars... Another totally useless reply from one of the GreatMinds at PerlMonks.
Have you googled for "unable to establish master SSH Connection: Unknown error"?
Didn't think so. If you had, you'd have seen that it returns two (2) hits, both of which are for the root node of this thread.
Shame on you! And to think others have probably up-voted such a pointless and unhelpful reply. But you seem to have a special knack for those. | [reply] |
Have you googled for "unable to establish master SSH Connection: Unknown error"?
Didn't think so.
As a matter of fact I did, and although these perlmonks nodes are mentioned, the first link I got back from Google was a node where it was pointed out it is usually a filesystem permissions error which spits out that message.
I didn't include the quotations in the search string. That explains the difference in our search results.
You show why you remain anonymous, since your programming troubleshooting techniques are so poor.
Bad wu wei man. You come here asking for free answers, then complain when you are not spoon fed an answer.
| [reply] |
Try again, dude.
These PM nodes are not only mentioned first, they are the only ones mentioned. (HINT: when searching for a specific error message, you need to quote the search string.)
I did not come here asking for answers, free or otherwise. Don't blame someone else for my node. Bad wu wei, indeed.
| [reply] |