Here is the code I was using that is now broken. I have defined $dbh as a global variable using 'our' pragma.
if (my $pid = fork) {
l("D","$restr [$tbn] [se_id:$se->{scenario_exec_id}] forking ($p
+id) $se->{suite_name}:$se->{scenario_name}");
$V{scenario_exec_childs}->{$se->{scenario_exec_id}}{pid} = $pid;
$V{scenario_exec_childs}->{$se->{scenario_exec_id}}{start_time}
+= $before_exec;
# prepopulate before next cycle for state consistency, $se is re
+ferenced in the $ses array ref in main loop
$se->{status} = "RUNNING";
set_scenario_exec_state($se,{ -testbed_id=>$tb_id, -pid=>$pid, -
+start=>"now()", status=>"RUNNING" });
sleep 2;
} elsif (defined $pid) {
$0 = "$restr $tbn SE:$se->{scenario_exec_id}";
l("D", "top of se fork: " . $dbh);
# once and for all, I think I have figured out the forking + DBI
+ connection handling issue! 2007-04-23,
# we clone the handle, undef it, then copy over the old variable
+ in the new process
# suppress warning from clone call... I think something is broke
+n with DBI
# produces: Can't set DBI::db=HASH(0x82cf704)->{User}: unrecogni
+sed attribute or invalid value at
# /volume/perl/lib/site_perl/5.8.5/i386-freebsd/DBI.pm line 648.
my $saved_warn_handler = $SIG{__WARN__}; $SIG{__WARN__} = sub {}
+;
my $child_dbh = $dbh->clone(); $SIG{__WARN__} = $saved_warn_hand
+ler;
l("D", "cloned child_dbh: " . $child_dbh);
$dbh->{InactiveDestroy} = 1; undef $dbh; $dbh = $child_dbh;
20090108 Janitored by Corion: Changed PRE tags to CODE tags, as per Writeup Formatting Tips
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.