in reply to Re: no sigchild under win32 ?
in thread no sigchild under win32 ?

The $SIG{CHLD} handler will not trap anything if you use Win32::Process. :-(

Replies are listed 'Best First'.
Re: Re: Re: no sigchild under win32 ?
by NaSe77 (Monk) on Jun 18, 2002 at 09:32 UTC
    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]

      Umm, I'll be the first to admit that signal handlers are most likely my weakest area of expertise, but it seems pretty clear that the code you give and the error are for two different things, one named SIGCHLD and one SIGCHILD. Did you copy and paste the actual code you used?

      -Mike-
[reply]
        peripc - signals

        'Perl uses a simple signal handling model: the %SIG hash contains names or references of user-installed signal handlers.'

        Simply put, SIGCHILD, SIGCHLD should be $SIG{CHLD}, $SIG{CLD}. Even so, the code should read something like kill($signal, $processid).

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom