I am using a library that starts lots of threads. It is a proprietary lib and there is no choice as it talks to some company's fancy schmancy hardware. The problem I have is that, it seems (strace is great), this library does not set it up so the threads it creates will not receive signals. In my own much-better-behaved-if-I-do-say-so code, I use pthread_sigmask in the created thread to say that I do not want various signals. Since I see my SIGIO signal delivered to both my thread (really the original process not a thread) or any of the threads created in the library, I think this is what is happening. My question is: how can I turn off delivery of signals to threads I did not create? I basically need to try to do for the threads what they did not do themselves. Add to that: how can a process find out what threads there are? I would imagine that if signal fiddling is even possible, I may need to know this as well. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-programming+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-programming+help@opensuse.org