You need to handle SIGCHLD signals. When a child process exits, the parent gets a SIGCHLD. There, you call waitpid() to get the exit status of the child.

This is from my own Tk based mp3 player:

#start a new song $SIG{'CHLD'} = 'sig_child'; if ($pid = fork) { $w::main->configure( -title => "TkMP3 - $fnm" ); $w::title->configure( -text => $fnm ); } elsif (defined $pid) { exec 'kmp3player','-q','-b','256',$fnm; } else { die "Can't fork: $!\n"; } # the child exit handler sub sig_child { $wsts = waitpid($pid,WNOHANG); $sts = $?; if ($wsts == 0) { $SIG{'CHLD'} = 'sig_child'; return; } die "Child exited abnormally, exiting\n" if $sts != 0; # send notification to app to pick next song #....
}
--- print map { my ($m)=1<<hex($_)&11?' ':''; $m.=substr('AHJPacehklnorstu',hex($_),1) } split //,'2fde0abe76c36c914586c';

In reply to Re: tk player with system/exec by pfaut
in thread tk player with system/exec by mce

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.