Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47456 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 59808 invoked from network); 22 Mar 2010 16:09:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Mar 2010 16:09:04 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.216 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.218.216 mail-bw0-f216.google.com Received: from [209.85.218.216] ([209.85.218.216:50747] helo=mail-bw0-f216.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 74/69-14451-F1697AB4 for ; Mon, 22 Mar 2010 11:09:04 -0500 Received: by bwz8 with SMTP id 8so308925bwz.23 for ; Mon, 22 Mar 2010 09:09:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=hsiQNLr/VhSCJZ3DTdraKDEPnIgssQIyprgOxffRRV4=; b=anJzagyhWppESM9r2wOx2S8cyRlfFwEFSU5Qnt1JrGkCENfLCzkNnN3112mgdyj9l1 oIiuuO3HJsbrTKPJO9lt4B8R2xC9DdhX5PnnBbbAA0Q9DD+LvyJ1iU9SrhhoINo/2zLP p4Qldr50ktLCI6WrZMBQ7yPokII7akthNhtAU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=qhMqhtlggsmLzc2tkZlXG+sRZZBTWmppNTQb4WBiqnT8WRqpUVoF1zfEApl2G6tK7r SgMPqxhg+SJvAs+K4D/QoMFJSAuU1JDzMutgCwVwOutM6Vea3Cnvo3u3iwwBTqKzKUb3 2VQkCYcGGXVKSHTnzFUEZsIZxAh+wu1S9uybc= MIME-Version: 1.0 Received: by 10.204.48.136 with SMTP id r8mr4619432bkf.120.1269274140496; Mon, 22 Mar 2010 09:09:00 -0700 (PDT) In-Reply-To: References: <98b8086f1003220751j73a8414es89b9b469c46f6630@mail.gmail.com> <1269270852.1575.141.camel@guybrush> <98b8086f1003220822s47665f87x696b70e9c13dadbd@mail.gmail.com> <98b8086f1003220855ya52c266g8dc4cb866ed451ea@mail.gmail.com> Date: Mon, 22 Mar 2010 17:09:00 +0100 Message-ID: To: Herman Radtke Cc: troels knak-nielsen , PHP Developers Mailing List Content-Type: multipart/alternative; boundary=00032555b2a24455ad048265ea1b Subject: Re: [PHP-DEV] [PATCH] Raise warning first on "Maximum execution time exceeded" From: tyra3l@gmail.com (Ferenc Kovacs) --00032555b2a24455ad048265ea1b Content-Type: text/plain; charset=UTF-8 On Mon, Mar 22, 2010 at 5:04 PM, Herman Radtke wrote: > > This patch handles timeout, not memory exhaustion. > > Apologies. My train of thought inexplicably switched over to memory. > I meant to assert that your custom error handler could extend the > length of the script to n extra seconds. This violates that idea of > the timeout. > try: time php -r 'set_time_limit(1);echo "start";register_shutdown_function(function(){sleep(10);echo "done";});' violates what? Tyrael > -- > Herman Radtke > hermanradtke@gmail.com | http://hermanradtke.com > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --00032555b2a24455ad048265ea1b--