I have a question in regards to page timeouts and how the initial
request is terminated.
First, I apologize up front for my ignorance. I am not a php user,
rather a database developer who has customers using php.
I've noticed if a query takes longer than the default 30 seconds to
execute, php
I have a question in regards to page timeouts and how the initial
I've noticed if a query takes longer than the default 30 seconds to
execute, php returns a timeout message to the user. From what I can
tell, php uses the SIGPROF signal to stop execution when the 30
seconds
has expired.
On timeout, the engine will call zend_bailout(), which performs a
longjmp(). It does unwind the stack, but since we're dealing with C and
not C++ and there are no destructors, it's your responsibility to clean
after yourself. You can do it by properly registering your resources with
PHP's
- Original Message -
On timeout, the engine will call zend_bailout(), which performs a
longjmp(). It does unwind the stack, but since we're dealing with
C and
not C++ and there are no destructors, it's your responsibility to
clean
after yourself. You can do it by properly
At 17:05 20/02/2003, [EMAIL PROTECTED] wrote:
- Original Message -
On timeout, the engine will call zend_bailout(), which performs a
longjmp(). It does unwind the stack, but since we're dealing with
C and
not C++ and there are no destructors, it's your responsibility to
clean
after
Suraski [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 20, 2003 8:16 AM
To: [EMAIL PROTECTED]
Cc: Jeremy Mullin; [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] zend_timeout and the SIGPROF signal
At 17:05 20/02/2003, [EMAIL PROTECTED] wrote:
- Original Message -
On timeout, the engine
At 17:20 20/02/2003, Jeremy Mullin wrote:
Don't call malloc? Wow, that puts some serious restrictions on what an
external library can do. :)
In the code that you control, obviously.
Couldn't drivers be required to implement something like SQLCancel in
ODBC? A mechanism that lets the driver
At 16:58 20/02/2003, [EMAIL PROTECTED] wrote:
I have a question in regards to page timeouts and how the initial
I've noticed if a query takes longer than the default 30 seconds to
execute, php returns a timeout message to the user. From what I can
tell, php uses the SIGPROF signal to stop
- Original Message -
I looked into the bug report, and it is true that
BLOCK_INTERRUPTIONS
should indeed block SIGPROF. I'll fix this in the weekend.
I'm not sure if after unblocking interruptions PHP will get SIGPROF ...
it could cause long scripts. I'd rather use EG(timeout).
At 17:38 20/02/2003, [EMAIL PROTECTED] wrote:
- Original Message -
I looked into the bug report, and it is true that
BLOCK_INTERRUPTIONS
should indeed block SIGPROF. I'll fix this in the weekend.
I'm not sure if after unblocking interruptions PHP will get SIGPROF ...
it could cause
On Thu, Feb 20, 2003 at 05:48:29PM +0200, Zeev Suraski wrote:
At 17:38 20/02/2003, [EMAIL PROTECTED] wrote:
- Original Message -
I looked into the bug report, and it is true that
BLOCK_INTERRUPTIONS
should indeed block SIGPROF. I'll fix this in the weekend.
I'm not sure if
On Thu, Feb 20, 2003 at 05:11:55PM +0100, Wojtek Meler wrote:
On Thu, Feb 20, 2003 at 05:48:29PM +0200, Zeev Suraski wrote:
At 17:38 20/02/2003, [EMAIL PROTECTED] wrote:
- Original Message -
I looked into the bug report, and it is true that
BLOCK_INTERRUPTIONS
should
12 matches
Mail list logo
