> Kernel.system forks and execs a new process for the command (via the
> C library version of system()) so I don't see how threads in the
> jmeter process could be affected at all by anything Ruby is doing.
> In fact Ruby isn't really 'doing' anything other then waiting for
> the child process to complete.

That's excellent info, thankyou. It will help a lot in what I choose to 
focus on in terms of debugging efforts.
-- 
Posted via http://www.ruby-forum.com/.