Ahhh, in that case, I'll switch to Apache 1.3. I'm all for safe code, but when using third party libs, you can't guarantee it'll do what you want, regardless of the failsafes you lay down.
Lee -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nicolas Cannasse Sent: 23 August 2006 09:28 To: Neko intermediate language mailing list Subject: Re: [Neko] Mod_neko on Apache 2.0.x > Oh, no no, those kinds of errors are fine, but oftimes, when creating my > own neko modules, they can sometimes cause neko to fail which causes > Apache to shut down. You mean, for example if you have a bug in one of your C libraries ? In general, all Neko C libraries should be "safe" and not crash, but there is sometimes nasty bugs :) Apache 1.3 is safe for this since if one process fails, the other processes (including the "main" one) will not get affected. This is not the case with Apache 2.0 (which is one-process, multiple-threads), but I'm not sure if it's possible or not to configure it to automaticaly restart when an error occurs. Nicolas -- Neko : One VM to run them all (http://nekovm.org) -- Neko : One VM to run them all (http://nekovm.org)
