in reply to Re^2: Trying to thread a daemon with threads and Thread::Queue
in thread Trying to thread a daemon with threads and Thread::Queue

What am I doing wrong?

Your using the "new" version of Thread::Queue which used to be a simple, reliable and fast module, but now someone has taken it upon theselves to "enhance" it, and in the process they have fu**ed up the single most useful, most reliable threading module.

Is there any process for banning people from messing with things that work?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."
  • Comment on Re^3: Trying to thread a daemon with threads and Thread::Queue

Replies are listed 'Best First'.
Re^4: Trying to thread a daemon with threads and Thread::Queue
by jasmineaura (Initiate) on Aug 27, 2008 at 20:32 UTC
    OH DARN!!! I was hoping I was doing something wrong :(
    That might explain all the "failed to dup 'weird symbols'" i was getting in the log (while i was using another version of my script during trial and error) when i had a dienice("$_") message after:
    open my $socket, '+<&=' . $fno;

    Is there any workaround? alternate solution/module to use? I can't force everyone who uses my script to downgrade to an older version of Thread::Queue just to get it to work :(

    Might want to try threads::shared perhaps ?
[reply]

In Section Seekers of Perl Wisdom