Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:28725 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81668 invoked by uid 1010); 10 Apr 2007 20:15:46 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 81638 invoked from network); 10 Apr 2007 20:15:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Apr 2007 20:15:44 -0000 Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.114 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 63.205.162.114 unknown Windows 2000 SP4, XP SP1 Received: from [63.205.162.114] ([63.205.162.114:17802] helo=us-ex1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6D/8E-17137-660FB164 for ; Tue, 10 Apr 2007 16:15:42 -0400 Received: from [127.0.0.1] ([192.168.16.109]) by us-ex1.zend.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Apr 2007 13:15:31 -0700 Message-ID: <461BF02C.7030105@zend.com> Date: Tue, 10 Apr 2007 13:14:36 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: David Sklar CC: internals@lists.php.net References: <7cea347c0704040255o525a1ebdy81e4b5dbad047baa@mail.gmail.com> In-Reply-To: <7cea347c0704040255o525a1ebdy81e4b5dbad047baa@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Apr 2007 20:15:31.0253 (UTC) FILETIME=[FCFF4E50:01C77BAC] Subject: Re: [PHP-DEV] max_execution_time - ITIMER_REAL vs ITIMER_PROF From: stas@zend.com (Stanislav Malyshev) > 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? IIRC at least on some systems ITIMER_REAL is the same as alarm(), and Apache uses alarm(), so we might have a conflict there. -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/