Hello Monks I have an odd problem. We are running dual core pentium 4's with hyper-threading enabled. The perl scripts that we have run threads or multiple threads. And run just fine with the hyper-threading enabled. We ran into a machine with hyper-threading DISABLED, and the scripts did not even get off the ground. We had our first print statement execute, then the threads went into lala land. The threads are created and join'd as follows: 
foreach $host (@syshosts)                
{    
    threads->new(\&locateSysHost_Parallel, $host);
}                        
(threads->list)[0]->join while threads->list;

[download]
When we changed the join to 
foreach $host (@syshosts)                
{    
    threads->new(\&locateSysHost_Parallel, $host)->join;
}

[download]
the threads ran as we expected. Has anyone else had these weird issues occur?

In reply to perl threads and dual core hyper-threading by JFarr

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.