Ampersands and accidental backgrounding aside, it's also possible that system encountered a problem but since you have no error checking on the call it's blithely continuing on to the next iteration immediately with no indication a failure occured.

$ perl -le 'for (0..3) { system( "Idonotexist $_" ) }'
$ perl -le 'for (0..3) { system( "Idonotexist $_" ) == 0 or warn "syst
+em problem (exit $?): $!\n" }'
system problem (exit -1): No such file or directory
system problem (exit -1): No such file or directory
system problem (exit -1): No such file or directory
system problem (exit -1): No such file or directory
$
[download]

Update: Not to say that's what happened here since as you say you did see a lot of processes running; just that in general it pays to take the extra 15 seconds and put the error handling in place.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.