Re: Trouble passing an array reference to my threads

[NetWallah]

The thread inherits a COW (Copy on write) copy of a part of the array, so updates to that will not affect the original.

What you need to do is to RETURN a value from your "sub pinger". This value can be collected when the thread is join()ed.
Use the returned value (Which can be an array ref, in fact, you can return $task) to update the array.

FWIW, I find the code style you used frightening, but am resisting the urge to comment on that. Should you choose to approach that subject, please request comment. I'm sure monks would be more than happy to share coding tips.

[zwon]

The thread inherits a COW (Copy on write) copy of a part of the array

There's no COW, it's just a copy created the same time the thread created.

[NetWallah]

You are probably right - I made some assumptions based on my (limited) understanding of how threads are implemented - I thought I read somewhere that there is an underlying fork, which does COW.

[zwon]

I think it is exactly opposite -- fork emulation implemented using threads on Windows

[dh]

I don't want to frighten anyone with my code. This code was pulled out of the full script, so it may be more frightening in fragment than its original.

Some of the mess in the code, like not returning from the threads, comes from the fact that this code wasn't threaded until I realized there may be too many hosts to iterate quickly enough. Originally, it just passed from sub to sub for each host in step. I am going to try returning that value from a join tonight to keep the reference inside the thread caller.

I would absolutely like to hear your comments on how the style and methodology may be improved. This code will be running for a while, so I want it to run well.

Thank you!