I may be missing something, but is there anything wrong with fork? 
#!/usr/bin/perl
use strict;
use warnings;
use POSIX ":sys_wait_h";

$|++;

print "Content-type:text/plain\n\nStarting script.....\n\n";

my $pid;
if (!defined($pid = fork)) {
    die "Could not fork! $!";
}
elsif ($pid) {
    # parent - clean up when child exits
    1 while (waitpid($pid,WNOHANG) != -1);
    cleanup();
    exit(0);
}
else {
    # child - does the processing
    print "Processing...\n\n";
    sleep(5);
    print "Finished...\n\n";
    exit(0);
}

sub cleanup {
    # do the clean up here
}

[download]

In my test CGI $|++ doesn't seem to do anything. I can't work out why the output appears buffered - is that a fork side effect?

cLive ;-)

In reply to Re: cleanup a cancelled CGI script by cLive ;-)
in thread cleanup a cancelled CGI script by goofball

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.