I believe that in CGI or CLI process you'd be okay, as the "fork" happens in its own process, and can only mess up PHP, which is fairly safe. In PHP as Module, you risk thread-safety issues in a big way with any PHP extensions that aren't thread-safe. And nobody is 100% sure on any of the extensions (or anything else, really) being thread-safe or not. I suspect that in FCGI, you're in the same boat as in PHP Module, and the documentation hasn't quite caught up to FCGI as a paradigm, but I could be 100% wrong on that... On Thu, June 7, 2007 10:45 am, Nathan Nobbe wrote: > I was reading the handbook on the topic of Unix process control. The > first > thing it says is: > > Process Control support in PHP implements the Unix style of process > creation, program execution, signal handling and process termination. > Process > Control should not be enabled within a web server environment and > unexpected > results may happen if any Process Control functions are used within a > web > server environment. > > Does this mean that a machine running PHP to handle HTTP requests > should not > also use PHP to implement a Unix style process, or does it mean that > these > methods should not be called from the CGI > SAPI<http://www.php.net/manual/en/features.commandline.php> > . > My impression is that a given machine should be able to use the Unix > process > control functions and handle HTTP requests as long as the Unix process > control functions are invoked strictly from the CLI > SAPI<http://www.php.net/manual/en/features.commandline.php> > . > > can somebody clear this up for me? > > thanks, > > ~quickshifin` > -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
