Re^3: Waiting for multiple filehandles (threads)

and why do you have the $done shared? it's not being set to 1 anywhere, so i was just wondering

Because, for clarity, I cut down an existing script which monitors my firewall and modem logs. In the real script, the main thread also traps SIGINT, sets $done true and waits for the threads to terminate before ending.

I don't know of any good "perl + threads" tutorials. You could do a super search for my posts that contain "use threads", there are quite a few examples now, but be warned, I am still learning what is and is not possible to do and the best ways of doing things. Many of my earlier threads posts contain code which is moe complicated that necessary.

I'd try and put together some kind of tutorial on them, but I've only use threads and Perl on Win32. I have seen very little information about what works on other platforms, so it would have very limited scope.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco.

Rule 1 has a caveat! -- Who broke the cabal?

Comment on Re^3: Waiting for multiple filehandles (threads)

Replies are listed 'Best First'.
Re^4: Waiting for multiple filehandles (threads) by insaniac (Friar) on Mar 22, 2005 at 16:23 UTC
ah ok... so i'll just stick `perldoc threads`. thanks anyhow! to ask a question is a moment of shame to remain ignorant is a lifelong shame	[reply] [d/l]
Re^5: Waiting for multiple filehandles (threads) by BrowserUk (Patriarch) on Mar 22, 2005 at 16:52 UTC
so i'll just stick perldoc threads. That's okay as an API reference, but you did ask about tutorials. There is also perlthrtut, but I don't rate it particularly highly. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. Lingua non convalesco, consenesco et abolesco. Rule 1 has a caveat! -- Who broke the cabal?	[reply] [d/l]