Re^3: Interrupting a blocking read (Linux::Inotify2) with a signal handler within a thread

Then your simplest, best (and probably only) solution would be to switch the notify and processing threads around.

That is, put the event processing into the worker thread and run the Inotify in the main thread.

That makes more sense anyway as the Inotify only has to queue the events, but if the event are occurring rapidly, a single processing thread might not be able to keep up. By placing the processing in a worker thread, you can start 2 or 3 or as many as are needed.

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.

Comment on Re^3: Interrupting a blocking read (Linux::Inotify2) with a signal handler within a thread

Replies are listed 'Best First'.
Re^4: Interrupting a blocking read (Linux::Inotify2) with a signal handler within a thread by clueless newbie (Curate) on Sep 10, 2011 at 20:40 UTC
That seems to be the best way to "get-her-done", but it galls me that I don't understand how to get a signal handler in a thread to work! I thank you for your help.	[reply]
Re^5: Interrupting a blocking read (Linux::Inotify2) with a signal handler within a thread by BrowserUk (Patriarch) on Sep 10, 2011 at 20:53 UTC
it galls me that I don't understand how to get a signal handler in a thread to work The short answer is that they don't work in threads. Signals are sent to the process, not individual threads within it. The salient part of the relevant documentation for linux reads: A signal's disposition within a process's context defines what action the system will take on behalf of the process when a signal is delivered. All threads and LWPs (lightweight processes) within a process share the signal disposition, which is processwide and cannot be unique among threads within the same process. That said, threads belatedly acquired some additions that attempt to allow "inter-thread signalling", but in my limited experience of trying to use them, they are essentially useless, as they won't actually interrupt anything -- you have to poll to see if they have been received. 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.	[reply]
Re^6: Interrupting a blocking read (Linux::Inotify2) with a signal handler within a thread by clueless newbie (Curate) on Sep 10, 2011 at 21:03 UTC
Thanks, that explains why "I removed the Linux::Inotify2 code from the Watchdog and but still couldn't get either form of the signal handlers to work!".	[reply]