2010/11/3 Martin J. Evans <martin.ev...@easysoft.com>: [...] > From time to time something similar to Brian's post turns up on this list > although it is usually something to do with pipes not working as you expect. > > I have to say I would be strongly against returning all signals to their > original state after a connect call. I know for a fact that some oracle > clients (depending on how you connect to Oracle) install a SIGCHLD handler > for instance. Who is to say what operations in the Oracle client library > might be rendered useless if we destroy any signal handlers it has set up.
There is an entry in Oracle Knowledge Base about this. I had trouble with this in a project around a year ago - and under specific circumstances it's safe to restore the handlers and in others you should chain them (when you need them, too). Search for SIGCHLD in the knowledge base (I didn't took the URI with me when I left the contractor). > Is it really worth changing DBD::Oracle for what effectively is a one liner? No, because it's not safe for each Oracle configuration. It must keep up to the developer to figure out when it's safe. > Perhaps some better documentation on connect would suffice once we get to the > bottom of Brian's observation. Yes :) > Martin Best regards, Jens
