If I am using Apache having a pool of worker processes, and something of individuals launches its very own lengthy-running process, what goes on to that particular worker? Will Apache kill it eventually, killing the kid process? Will that worker be permanently not available, but keep running? So how exactly does it differ whether it begins a thread rather than a procedure? So how exactly does it differ in a variety of web application deployment situations?
How's the lengthy-running process released? A cgi? If that's the case the apache worker process will sit and watch for your process to complete, however lengthy it requires, and also the it won't serve anymore demands. Should you stop apache the staff member process is going to be ended. What goes on for your process is dependent on which it will if this receives the word signal.