Re: [tbnl-devel] Help needed in handler function with (sleep seconds)
Stefan is perfectly right. mod_lisp2-3.c has some problem in managing timeout. where mod_lisp2-2.c (which is based on a different implementation) works has expected if the handler contains (sleep n). But since mod_lisp2-2.c occasionally crashes Apache and has no support for the latest Edi's improvements (since is based on mod_lisp 2.33) I would say that the option to move back to apache 1.3 with the latest mod_lisp.c 2.38 is still a good move, until someone (Marco Antoniotti & Co.) with enough experience has time to port and test mod_lisp.c 2.38 to Apache2. Stefan Scholl wrote:
On 2004-08-23 17:21:14, Edi Weitz wrote:
mod_lisp for apache 2
There are several versions as far as I know.
Hmm. http://www.fractalconcept.com:8000/public/open-source/mod_lisp/contrib/mod_l... has a timeout of 1 second and all ap_reset_timeout() and ap_kill_timeout() calls are commented out.
Haven't tried to understand the code, though. Just searched for "timeout".
Regards, Stefan
_______________________________________________ tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
-- ING. MASSIMILIANO CAMPAGNOLI PAOLO ASTORI SRL VIA MIRABELLA, 9 28013 - GATTICO ITALY
Chris Hansen asked me to forward the following message to this list. Note that he's not subscribed so you have to Cc him if you reply. Cheers, Edi. From: Chris Hanson <cph@zurich.csail.mit.edu> Subject: [tbnl-devel] Help needed in handler function with (sleep seconds) To: maxi@paoloastori.com CC: tbnl-devel@common-lisp.net, marcoxa@cs.nyu.edu Date: Sun, 05 Sep 2004 00:44:58 -0400 User-Agent: IMAIL/1.21; Edwin/3.116; MIT-Scheme/7.7.91.pre Date: Mon, 23 Aug 2004 19:07:50 +0200 From: Massimiliano Campagnoli <maxi@paoloastori.com> where mod_lisp2-2.c (which is based on a different implementation) works has expected if the handler contains (sleep n). But since mod_lisp2-2.c occasionally crashes Apache and has no support for the latest Edi's improvements (since is based on mod_lisp 2.33) I would say that the option to move back to apache 1.3 with the latest mod_lisp.c 2.38 is still a good move, until someone (Marco Antoniotti & Co.) with enough experience has time to port and test mod_lisp.c 2.38 to Apache2. I'm interested to know if there is a reliable way to crash apache using "mod_lisp2-2.c". If so, I'll fix it. I am also willing to update the implementation with the 2.38 improvements, provided that it doesn't take more than a day or so. The main problem is that I haven't been using the module. (I'm still using Apache 1.x.) I wrote the module for a colleague, so that he could use my server-side software, and I haven't heard about any problems from him. Are there any other known problems with this code?
participants (2)
-
Edi Weitz -
Massimiliano Campagnoli