I have a newsletter script written in Perl (I'm a not the author) that can be called and administered from a Web page. It forks, and the parent responds to the web client saying that the child process is working but could take some time (depending of the number of registrations you deal with) while the child carries on with the job.

The script worked on bigger servers. Now I'm trying to run it on my own and the process just hangs their until its all completed before giving control back to the user.

Is there a configuration line in apache that deals with the issue if scripts can succesfully fork and not hog the user's browser ?

Thanks.