comment on

So yeah, Net::SSH::Expect is probably thread safe.

That is a miserable thing to do to a beginner Anon.

You might have finished the quote from the Expect POD which goes on to say:

The reason is that spawn() uses fork(), and perlthrtut:
"Thinking of mixing fork() and threads? Please lie down and wait until the feeling passes."

which whilst having more in common with the old map notations, "there be dragon's here", than rational or tested advice, probably does mean that if you venture beyond that point, you will likely be on your own and are going to be breaking new ground.

Throwing "So yeah" at a (threads) beginner is just mean.

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.

The start of some sanity?

In reply to Re^2: Is Net::SSH::Expect a thread-safe module? by BrowserUk
in thread Is Net::SSH::Expect a thread-safe module? by ashok.g

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl Monk, Perl Meditation
	PerlMonks