(Assuming the answer to my question above is yes.)

The problem is that you are creating asynchronous processes, but never gathering their return codes via wait or waitpid.

In order to provide a way to retrieve the exit codes from asynchronous processes, the windows implementation has an internal limit of 64 un-waited asynchronous processes. Call one of the above two calls once the process has finished, and you will "fix" the problem.

That said, if your code is starting one process at a time, and then hanging around polling a 'lock' file before continuing; why on earth are you using asynchronous processes and lock files?

If you just called the synchronous variant of system, you wouldn't need the lock files, or to call wait/pid.

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.

In reply to Re: what are the common causes of "system" command failure on Vista by BrowserUk
in thread what are the common causes of "system" command failure on Vista by Workplane

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.