I tried closing STDOUT, STDIN and STDERR with no apparent difference. A further oddity I've noticed is that when it does actually finish (by running a 'long' program that isn't really all that long), the page returned by Apache from the CGI contains two copies of the message, though only one copy of debug messages in the log.

My code now looks like this, including the bit of code before the extract I showed

binmode(STDOUT, ":unix"); # unbuffer STDOUT print $q->header( -status => '200 Pages Updated', -type => 'text/plain', -charset => 'ascii', ); print "\n\nStarting Update of $app_name\n\n" . "Since this will take a while, we will send a mail " . "when it is complete\n"; warn "Forking '@cmd'\n" if $DEBUG; use Proc::Daemon; my $daemon = Proc::Daemon->new( ); close STDIN; close STDOUT; close STDERR; my $child_pid = $daemon->Init; if ($child_pid) { # We are the parent - we need to exit so Apache shows what # we just printed to the user # warn "Child PID is $child_pid\n" if $DEBUG; exit; } my $status = system @cmd; # send an email after completion instead of updating the page

The 'Starting Update...' text appears twice on the HTML page, but the 'Forking...' message only appears once in the log. A single email message is sent as well.


In reply to Re^2: Proc::Daemon not detaching by Dave Howorth
in thread Proc::Daemon not detaching by Dave Howorth

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.