<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sat, 25 May 2013 00:53:42 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Chris Jones' Blog: PHP OCI8 Signal Handling and --enable-sigchild]]></title>
      <guid>http://www.phpdeveloper.org/news/12205</guid>
      <link>http://www.phpdeveloper.org/news/12205</link>
      <description><![CDATA[<p>
<i>Chris Jones</i> has <a href="http://blogs.oracle.com/opal/2009/03/php_oci8_signal_handling_and_e_1.html">changed his stance</a> on something he's been recommending PHP users compiling the OCI8 libraries into their installation - the use of enable-sigchild.
</p>
<blockquote>
I am no longer blindly recommending using --enable-sigchild when configuring PHP with the OCI8 extension. I used to do this as a catch-all. It might have saved some users grief, and did little harm. With changes in recent versions of Oracle and my gut feel about common usage, it will be less confusing not to mention it as a general suggestion.
</blockquote>
<p>
The point of using the compile flag was to help with the opening/closing of connections to Oracle server processes, but there's a better way he recommends now - using a "BEQUEATH_DETACH" option of "YES" in the sqlnet.ora/Apache config. If that doesn't work, then look into recompiling with the enable-sigchild option.
</p>]]></description>
      <pubDate>Wed, 25 Mar 2009 10:22:51 -0500</pubDate>
    </item>
  </channel>
</rss>
