That sounds promising. I will have to check threads and threads::shared as I in fact need (or wanted) to:

  1. Run several system commands in parallel
  2. Store the results in an sqlite DB
  3. Time out if a command runs too long

As it seemed to be not too easy to get the data from the parallel commands back to the parent, so that I just have one writer to the sqlite DB, I skipped this part for now and concentrated on the timeout part.

It seems with threads::shared, I can achieve what I wanted in the first place. Thanks BrowserUk!


In reply to Re^2: trying to get timeout to work (easier with threads) by Skeeve
in thread trying to get timeout to work by Skeeve

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