I have a multithreaded application that uses signals (SIGUSR1) internally.
It also uses log4cplus 2.0.3.
I see from the source that threads started with AbstractThread::start() indeed does block signals.
But the thread pool theads does not blocvk signals, resulting in my SIGUSR1 being handled by one of the thread pool threads instead of my own signal handler.

How can I prevent any thread started inside log4cplus from handling signals?

Regards
Klaus