I don't know how the Windows folks spawn their child processes, but in *nix, it's fork. For example: 

my $pid = fork();
if ( ! defined $pid ) {
    die "Can't fork: $!\n";
}
if ( $pid ) {
    # parent
}
else {
    # child
}

[download]

You could also look at Proc::Daemon which has this and more wrapped up in a tidy package.

Using a file to do your communication is a fine idea. To avoid polling, you could also use signals to let the worker know when to look. Have a look at the "Signals" section of perlipc.

In reply to Re: Managing a long running server side process using CGI by kyle
in thread Managing a long running server side process using CGI by GrandFather

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.