Cees Hek wrote:
Using fork is expensive. It will use up as much memory as the current child is already using, so you might as well just use the current child to finished the processing.
That will work only if you care to wait for all processes to finish untill you can restart apache. forking and detaching the process allows you shutdown your httpd servers without affecting your long term processes.
I guess it depends on how long the process is going to take. I should have mentioned that I would only use this for something that is going to run for a few minutes. Long enough for a user to get anoyed and be tempted to press stop or refresh in the browser.
If it is truely a long term process, then it will definately be better to fork (or to use the other suggestion of a daemon process looking for new work in a specified location)
Cheers,
Cees
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
