Hi Monks

Question regarding POE:Wheels, and they are are destroyed/reaped. Currently I use an approach where a message is sent to a Wheel, causing code in the child process to fall out of a loop and exit. This works fine but I get these annoying messages from the kernel:

!!! Child process PID:12793 reaped: 
!!! Child process PID:12795 reaped: 
!!! Child process PID:12791 reaped: 
!!! Child process PID:12794 reaped: 

All I am really after is a way to switch these messages off. Is there a better way to destroy a Wheel, or handle the reaping of a Wheel? I have tried registering the CHLD handler with the kernel, ie.

$_KERNEL->sig( CHLD => '_sig_child' );

While my _sig_child function is called, it doesn't suppress the kernel message.

Cheers

parsing XML is easy, said the data modeler to the programmer...you just look for an angle bracket and...


In reply to destroying/reaping a POE::Wheel by megamic

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.