Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

is there no signal send to the father process when a child dies under win32? i created a callback (at least i think i did) but it seems not to work : 
$SIG{CHLD} = \&dead_child;

sub dead_child{

       #do what is to be done

}

[download]

Replies are listed 'Best First'.
Re: no sigchild under win32 ?
by gumby (Scribe) on Jun 17, 2002 at 14:36 UTC
    Does your sub look like this? 

    sub dead_child {
  ...
  $SIG{CHLD} = \&dead_child;
}
$SIG{CHLD} = \&dead_child;

    [download]

    Upate: At the moment, what does your sub do?

[reply]
[d/l]
      no i dont have another callbak in the sub - why? do i need that?
[reply]
        Yes, you need to reinstate the handler. Read the perlipc man page.
[reply]
      concerning your updated question: it resets the status_field of my tk-frontend and opens the result-window
[reply]
Re: no sigchild under win32 ?
by Anonymous Monk on Jun 17, 2002 at 15:08 UTC
    perhaps it because i didnt use fork() or open() or something like that to create the childprocess but Win32::Process::Create ?

    so is there a signal send or another way to know if such a process is trerminated ?

[reply]
[reply]
[d/l]
      The $SIG{CHLD} handler will not trap anything if you use Win32::Process. :-(
[reply]
[d/l]
        why cant i just do something like 
        END{
    kill(SIGCHLD,$_parent);
}

        [download]
        in the child or so? in fact i tried this but i i got : 
        Your vendor has not defined POSIX macro SIGCHILD, used at $scriptname 
+line $line

        [download]
        and since my english is not too good i dont realy get what this means and what i should do
[reply]
[d/l]
[select]

Back to Seekers of Perl Wisdom