William T wrote:
There are all kinds of problems that you'll encounter and have to solve
if you fork. I found it's better to call at(1) to start another
seperate process immediatly. If you need to pass data JSON worked
really well for me.
Thanks, that's what I ended up doing. First I ended
There are all kinds of problems that you'll encounter and have to solve if
you fork. I found it's better to call at(1) to start another seperate
process immediatly. If you need to pass data JSON worked really well for
me.
-wjt
On Aug 25, 2009 5:12 AM, "Victor Danilchenko" wrote:
Hi all
my solution is here:
sub fork_temporary_child {
my $result = fork();
unless( $result ) {
# Do not use SQL in child
dbh->{InactiveDestroy} = 1;
disconnect_dbh;
}
return $result;
}
On Tue, Aug 25, 2009 at 7:11 AM, Victor Danilchenko wrote:
>Hi all,
>
>I need t
On Tue, Aug 25, 2009 at 8:11 AM, Victor Danilchenko wrote:
> I need to be able to fork an Apache process in daemon form, to do
> some housekeeping which might potentially take a few seconds. However, when
> I do that, I start getting SQL errors (of the "connection lost" type) in the
> browse
Hi all,
I need to be able to fork an Apache process in daemon form, to do some
housekeeping which might potentially take a few seconds. However, when I
do that, I start getting SQL errors (of the "connection lost" type) in
the browser. I do the fairly standard cleanup to daemonize the
