I am not sure, but I think it could have something to do with the value of the Timeout parameter. If your CGI does not send any information during a five minute interval (300 seconds), Apache will time out the request, and it is then very likely that the CGI process will die. If you do not know how long your CGI will take to complete, you may need to have the CGI send some bytes now and then in order to keep the connection alive. Otherwise you may want to increase the value of the Timeout parameter. Look at the manual pages for more info. -ascs -----Message d'origine----- De : Jain, Abhay K, ALABS [mailto:jainabhay@xxxxxxx] Envoyé : vendredi 8 avril 2005 20:35 À : users@xxxxxxxxxxxxxxxx Objet : [users@httpd] Treatment of child process of a CGI I have a CGI script that forks a shell script S. This shell script starts some other process X and waits and does some cleanup. Everything works fine if the shell script is finished with 5 minutes or so. However after 5 minutes, the cgi script dies. Shell script S is still waiting around. When child X finishes, it seems that shell script dies without finishing up any cleanup. What is happening here. I have ported web server from Netscape to Apache and Netscape allowed Shell S to finish up. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|