[Boost-users] [test] Still SIGCHLD issues?

Hi, I'm in progress of updating some projects to use Boost 1.40 (upgrading from 1.34.1). Everything now works fine under Windows, but under Linux there are issues with running unit tests that spawns and control child processes. My tests now report fatal errors and stops responding. Searching the archives I see several references to a problem with SIGCHLD, but no fix seems to have been issued. I'm sure there is a valid reason for treating SIGCHLD as errors, but does it really need to be enabled by default? Seems like a regression to me. Is it possible to disable this without patching Boost.Test? I'd really, really, really like to not go that route. Regards / Johan