Thanks Jeroen,
Somewhere in my quest to solve this issue, I read to first
unset the child signal with
$SIG{CHLD} = 'IGNORE'; ## Children die unnoticed ...
and then in the child use
setsid or die $!;
which supposedly immediately dissociates the child from the
mother, which means the mother doe
Well Tielman,
I think you are lucky that you don't have to catch the status of your
children!
Just one comment about: $SIG{CHLD} = 'IGNORE'; ## Children die unnoticed ...
I don't know exactly what your child does but if your child starts another
process again, you might run in trouble.
I code
Thanks Jeroen,
Somewhere in my quest to solve this issue, I read to first
unset the child signal with
$SIG{CHLD} = 'IGNORE'; ## Children die unnoticed ...
and then in the child use
setsid or die $!;
which supposedly immediately dissociates the child from the
mother, which means the mother doe
Read the docs, e.g., $dbh->{InactiveDestroy}
Tim.
On Tue, Oct 07, 2003 at 12:31:47PM +0100, tvilliers wrote:
> Hi,
>
> I have a mother process which needs to fork off a child at every x
> milestone. The child performs a small function (ie, write to a log) and
> then dies. The general idea is tha
Hi Tielman,
I had exactly the same problem (I asked about it about 2 weeks ago).
I use Oracle though. Even if you don't use the handle from the mother in the child,
the handle still gets fucked up. The child will try to close your handle.
There is a modifier called InactiveDestroy, like:
$db-
Thanks John,
But the idea here is that the child doesn't need a handle at all -- I
just want the mother's handle to be "left alone" ...
Tielman
On Tue, 07 Oct 2003 09:09:58 -0400, John Saylor wrote:
> hi
>
> no- fork YOU and die ...
>
> ( 03.10.07 12:31 +0100 ) tvilliers:
>> I have a mother
hi
no- fork YOU and die ...
( 03.10.07 12:31 +0100 ) tvilliers:
> I have a mother process which needs to fork off a child at every x
> milestone.
> Now, the mother has an open database handle, which from my understanding
> gets transferred to the child at fork. I want the handle to stay with the
Hi,
I have a mother process which needs to fork off a child at every x
milestone. The child performs a small function (ie, write to a log) and
then dies. The general idea is that the mother is unaffected by any
problems the child may encounter (ie, a closed socket, a full disk, eg).
The child fork
