Steve Hay wrote:
Oh yes! That kills the server itself! i.e. api.t now crashes the server in the course of executing its test plan, and ithreads doesn't even have a server to play with :(
Crashes? CORE::exit() works fine here (happened to work fine?). I guess it should be a problem since it'll kill any other running threads.
Maybe "crash" was too strong a word. What I meant was that the Apache.exe process exits, so now ithreads.t fails since there is no server running for it to connect to.
OK, that's better :) But doesn't Apache start a new process then?
As I understood it, this is exactly what overriding exit() was intended to prevent.
Exactly
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
