note Corion <p>I'm not sure what your threads are supposed to do with the currently running requests. I would let them finish their current request and have them recheck a global, shared flag whether to pause or (re)start processing. A more convoluted alternative would be to <c>$queue->unshift</c> dummy jobs on the threads work queue that tell each thread to pause.</p> <p>If the request <i>really</i> is "stop whatever you're doing", have a look at the "suspend" example in [mod://threads]. It seems to use signals, but as the signals are claimed to stay within the confines of Perl and seem not to be OS signals, these should be saner/safer to use with threads.</p> <p>If the request only means "don't update the widget", that's easy. Have your threads send the updates to the main program through a Thread::Queue, and then either fetch or discard the log updates from that queue.</p> 860078 860078