Actually we've run into similar problems as those habit_forming mentioned (defunct processes, unkillable children(hung on sockets), out of semaphore space errors, etc) when we've tried to fork children from code running under mod_perl. Our testing during development was mostly from the command line and via CGI, then basic checking that it works under mod_perl - which it generally does until its under load, then we get the problems.
The child we were spawning was running a command over ssh that might take a while to complete. I know mod_perl and other persistent Perl environments require a clean lifecycle of the code they run, but are there other requirements for forking code under mod_perl?
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.