Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28672
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.132.244 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=r427t8VpIph8EwEpkkZndXONz0OhMW8M3bK5W3NlEcFPWCGMxxtJgfYxvuz3bHlTYp2nQm6SDDdLbVHLfCIG05NG+WKnzBw1YD0aGuHbl3QLWIAWN6BlETlljgTJvvaNWHiLEcUI6kQl/Spn/WfG+yThpMGiocBz6tHQ00IthtU=
Message-ID: <7cea347c0704040255o525a1ebdy81e4b5dbad047baa@mail.gmail.com>
Date: Wed, 4 Apr 2007 11:55:56 +0200
To: internals@lists.php.net
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: max_execution_time - ITIMER_REAL vs ITIMER_PROF
From: david.sklar@gmail.com ("David Sklar")

I'm interested in having a timeout that corresponds to clock time as
opposed to PHP execution time (the current behavior of
max_execution_time). A cursory scan of the source implies that (on
Unix at least) something that behaves like zend_set_timeout() but uses
setitimer()'s ITIMER_REAL timer instead of ITIMER_PROF would do the
trick. Before I investigate much further, a few questions:

- Is anyone aware of a reason why ITIMER_REAL would cause problems?
(Signal delivered while PHP is doing something uninterruptable?)
- Assuming ITIMER_REAL works OK, is there interest in incorporating a
patch for a "max_real_time" config directive / timeout?

Thanks,
David