Re: Ruby Timeout

Hi,

At 02/07/06 17:09:40 (JST),
[email protected] (Dirk Meyer) wrote:
> I found some problems with mod_ruby on FreeBSD.
>
> When uploading files to a mod_ruby script,
> I get this error:
>
> [Tue Jan 24 13:39:23 2006] [notice] child pid 5161 exit signal
Segmentation fault (11)
>
> After I had enabled threads in ruby itself.
> apache13 could not load mod_ruby, i hand to relink mod_ruby to bind
> with the threadling lib, as apache13 is build withouth threads.

Does `enabled threads' mean --enable-pthread?
Then, do you need any library that uses pthread?
If not, you don't need to specify --enable-pthraed.
Ruby threads are available without --enable-pthread.

> Problem:
> If "RubyTimeOut" is set to a value greater then "TimeOut" in httpd.conf
> mod_ruby crashes (without threads), or aborts (with threads).
>
> Workaround, use insane values for the counters and stay without threads.
> RubyTimeOut 3000
> TimeOut 3600

I commited a change not to disable RubyTimeOut if RubyTimeOut is greater
than or equal to TimeOut.

> Does "RubyTimeOut" make sense with a threaded ruby?

It seems to work on my Linux box, but it may not work on FreeBSD:(

Shugo