Your premise that the child process doesn't call exit is wrong. Either it exited properly by calling exit with an exit code (setting $?'s high byte) or it was terminated by a signal (setting $?'s low byte). There's no other way for it to exit.

I thought exec executes a system command and never returns..

Same goes for the call to exit it's replacing.

Also, why is 'exec' preferred over 'system + _exit' ?

You're creating a process whose sole purpose is to do nothing but create a process, and you're doing that for as many hosts as you have in your array. It's wasteful! It also requires more code and introduces problems (refer to the bug I mentioned it fixed).

In reply to Re^5: Parallel::ForkManager run_on_finish exit code handler by ikegami
in thread Parallel::ForkManager run_on_finish exit code handler by sojourn548

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.