I'm satisfied. Thanks!
Ed Hingsbergen
Xchanging
300 W. Wilson Bridge Road
Suite 200
Worthington, OH 43085-2286
Office: 614.987.1582
Web: www.xchanging.com
Show quoted text-----Original Message-----
From: Martin J Evans via RT [mailto:bug-DBD-Oracle@rt.cpan.org]
Sent: Thursday, December 30, 2010 1:21 PM
To: Hingsbergen, Ed
Subject: [rt.cpan.org #16548] Child processes with certain connect
methods
<URL:
https://rt.cpan.org/Ticket/Display.html?id=16548 >
On Fri Dec 16 13:35:44 2005, guest wrote:
> DBD-Oracle-1.16
> DBI-1.49
> perl v5.8.6
> AIX 5.2.0.0
> Oracle 10.1
>
> Certain connect methods lead to problems with child processes.
> The following code:
>
> use DBI;
> $dbh = DBI->connect('dbi:Oracle:', $ENV{DBUSER},
> $ENV{DBPASSWORD});
> print `uname`;
> print "$!\n";
>
> Prints:
> AIX
> There are no child processes.
>
> If instead I use:
> $dbh = DBI->connect("dbi:Oracle:host=$host;sid=$ENV{ORACLE_SID}",
> $ENV{DBUSER}, $ENV{DBPASSWORD});
>
> The result is:
> AIX
> There are no child processes.
>
>
> In the first case, the $! content is erroneous. All backtick
> executions after the cinnect result in the same permissions message.
>
> In the second case, the message is also obviously wrong. I also get
> incorrect return values from the "kill" function.
>
>
> I rebuilt the DBI and DBD modules with no change. (To get DBD to make,
> I had to edit the Makefile to refer to the lib32 directories)
>
> How do you suggest I pursue this further?
>
> Thanks!!
This rt is very old now and I'm trying to clear the rt queue up for
DBD::Oracle. The issue with SIGCHLD is fairly well known now as is the
workaround Tim provided. Would you be happy for me to close this rt now?
Martin
--
Martin J. Evans
Wetherby, UK
Cambridge Integrated Services Group, Inc., Cambridge Galaher
Settlements and Insurance Services, Inc., and Scandent Group, Inc.
are members of the Xchanging group of companies.
This message and any attachment are confidential and may also be
privileged. If you are not the intended recipient of this e-mail
you may not copy, forward, disclose or otherwise use it or any part
of it in any form whatsoever. If you are not the intended recipient
please telephone or e-mail the sender and delete this message and
any attachment from your system.