in reply to Re: Gracefull Death of a Child: How to Catch Mum's SIGNALS?
in thread Gracefull Death of a Child: How to Catch Mum's SIGNALS?

I think he intends to send a SIGKILL: $D->kill('KILL') ...

The thing I wonder about is the signals themselves. When I think of signal handlers and things, I usually think of fork not threads... I'm very bad at threads so far though, so I could be wrong about that.

It would seem that the thread method $thrd->kill() sends a signal to the one thread. In all their examples, they use $thrd->kill("KILL")->detach (for cleanup); and the parent poster detaches before signaling. It makes me wonder if you can even do that... But, again, I don't really know.

update: oh, duh, you can't catch the 9th signal... way to go fletch.

-Paul

Replies are listed 'Best First'.
Re^3: Gracefull Death of a Child: How to Catch Mum's SIGNALS?
by BrowserUk (Patriarch) on Apr 04, 2007 at 08:52 UTC
    I usually think of fork not threads... I'm very bad at threads so far

    Tip. Don't even consider trying to use signals in conjunction with threads. Signals are an inter-process mechanism. All your threads are part of the same, single process.

    Whilst there may be some platforms out there that have adapted their threading and signalling libraries to work together in some non-standard but successful way, Perl's threading is not be coded to use those facilities, and probably never will.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom