-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Dunbar:
> Hmm is this when the setting was changed to kill FastCGI scripts after a
> minute or two when it used to be pretty much indefinite when wolfsbane
> was running on Linux?
there was no time or date or event of any kind mentioned in the
2009/8/19 River Tarnell :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Platonides:
>> I understand the problem was the process creation needed by mod_suphp
>> (that's also why the switchserver was tried).
>
> that is correct.
>
>> How does Zeus run the scripts as different users?
>
> it st
> we previously used Apache + mod_suphp, until CGI PHP became too slow.
> we explored several solutions and eventually settled on ZWS.
So then we should think about the setup on cassini, which uses
Apache + mod_suphp, and maybe make the change before it's populated with
tools.
Peter
_
Hi!
On Thu, August 20, 2009 11:49, River Tarnell wrote:
> seth wrote:
>> I'm not very experienced in rewrite-regexp. But in perl (and php's pcre,
>> ...) this would not be a good work-around, because the capture buffer
>> would sometimes be created and sometimes not.
>
> i was not able to reproduc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
seth:
> I'm not very experienced in rewrite-regexp. But in perl (and php's pcre,
> ...) this would not be a good work-around, because the capture buffer
> would sometimes be created and sometimes not.
i was not able to reproduce this behaviour, or els
Hi!
On Wed, August 19, 2009 22:55, River Tarnell wrote:
> after the web server change on Wednesday, we noticed the following
> behaviour of regexp matching in rewrite scripts: when using a construct
> like "(a|b|)", the regexp will *not* match the empty string. as a
> workaround, you can write "(
Would lighttpd/nginx be any better? I've had good experience with those.
Fahad Sadah
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list:
https://wik
River Tarnell wrote:
> Platonides:
>> I understand the problem was the process creation needed by mod_suphp
>> (that's also why the switchserver was tried).
>
> that is correct.
>
>> How does Zeus run the scripts as different users?
>
> it starts a FastCGI process as the user when a request come
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Platonides:
> I understand the problem was the process creation needed by mod_suphp
> (that's also why the switchserver was tried).
that is correct.
> How does Zeus run the scripts as different users?
it starts a FastCGI process as the user when a r
River Tarnell wrote:
> Martin Peeks:
>> Just out of curiosity, why does the toolserver use a webserver which so
>> few will be familiar with, rather than apache/etc?
>
> we previously used Apache + mod_suphp, until CGI PHP became too slow.
> we explored several solutions and eventually settled on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Peeks:
> Just out of curiosity, why does the toolserver use a webserver which so
> few will be familiar with, rather than apache/etc?
we previously used Apache + mod_suphp, until CGI PHP became too slow.
we explored several solutions and event
Hi,
River Tarnell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> hi,
>
> after the web server change on Wednesday, we noticed the following
> behaviour of regexp matching in rewrite scripts: when using a construct
> like "(a|b|)", the regexp will *not* match the empty string. as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
after the web server change on Wednesday, we noticed the following
behaviour of regexp matching in rewrite scripts: when using a construct
like "(a|b|)", the regexp will *not* match the empty string. as a
workaround, you can write "(a|b)?". if y
13 matches
Mail list logo
