That's exactly what a daemon parent is supposed to do: fork() a child into a detached state

Yes of course, a daemon closes all unnecessary file descriptors and forks itself and terminates, to detach from any terminal or I/O lines whatsoever. But in my book, the daemon does this right up front, before doing any other tasks.

But more to the point, I'm referring to the other child, then child resulting from the open($pipe, '-|', 'ip -o xfrm monitor')—that child.

Well, that child is kid of the daemons parent, so it might get reaped if grandfather exits. Perhaps reordering would help: 

my $pipe;

my $pid = fork();

if (! defined $pid) {
    die "couldn't fork";
elsif ($pid > 0) {
    # write $pid to .pid file
    cleanup();
    exit(0);                 ## problem happens HERE
}

## now in sub-process
close(STDIN);
close(STDOUT);
close(STDERR);
...

# open the pipe in the child only after daemonizing
open($pipe, '-|', 'ip -o xfrm monitor') || die "couldn't start sub-com
+mand";

while (my $line = <$pipe>) {
   ...
}

close($pipe);
cleanup2();
exit(0);

[download]
perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'

In reply to Re^3: What happens to a '-|' (pipe) file handle across a fork()? by shmem
in thread What happens to a '-|' (pipe) file handle across a fork()? by pprindeville

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.