Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47448 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31678 invoked from network); 22 Mar 2010 15:23:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Mar 2010 15:23:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=troelskn@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=troelskn@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: troelskn@gmail.com X-Host-Fingerprint: 209.85.218.216 mail-bw0-f216.google.com Received: from [209.85.218.216] ([209.85.218.216:64694] helo=mail-bw0-f216.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5F/23-14451-65B87AB4 for ; Mon, 22 Mar 2010 10:23:03 -0500 Received: by bwz8 with SMTP id 8so257996bwz.23 for ; Mon, 22 Mar 2010 08:22:59 -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 :content-transfer-encoding; bh=mcoqs3CspwUWdwbKpgwlVMtS4oGhWEMKMsUWv3nl0ao=; b=vhZQcmQl+ZII1E2sdSQjd9ln3zFGzdjpm8uss387Z7JhlLWJPeVjEmu5rzn3HSMDBD fr56b5sTi5cBPR0uXKkED9myvBYI6fvb1uCmuf9KjLU01PoaBRMkI45ZYZYRYQ/A3SLo cq6PRYbiapmTAZ30SBeUE02mHmfXr+1MafXb0= 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:content-transfer-encoding; b=ZOorJ5HytRSMDMtaOgHkfH8RKkr6+bwFDJbtUPvvZECkIzhvrVHhS5xhbX2LosWnu9 kM/d3o5hu/wh8UoRie1aYy3BZr3nEZdaWxIjEl8oySNVjsJq9olgvovFLxT83a6dezey z+tk6/nl65tVQHWrt+xwkaG/FGEVx0BwNdi7w= MIME-Version: 1.0 Received: by 10.204.131.207 with SMTP id y15mr4796101bks.69.1269271378948; Mon, 22 Mar 2010 08:22:58 -0700 (PDT) In-Reply-To: <1269270852.1575.141.camel@guybrush> References: <98b8086f1003220751j73a8414es89b9b469c46f6630@mail.gmail.com> <1269270852.1575.141.camel@guybrush> Date: Mon, 22 Mar 2010 16:22:56 +0100 Message-ID: <98b8086f1003220822s47665f87x696b70e9c13dadbd@mail.gmail.com> To: =?ISO-8859-1?Q?Johannes_Schl=FCter?= Cc: PHP Developers Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [PATCH] Raise warning first on "Maximum execution time exceeded" From: troelskn@gmail.com (troels knak-nielsen) 2010/3/22 Johannes Schl=FCter : > A one second delay is no option there. And what actually happens is that > the warning triggers your custom error handler. After that it sleeps > then it dies. What do you mean by "no option"? Otherwise yes, that's what it does. > This also creates a "nice" way to extend the script runtime after the > timeout occurred. aka. making the timeout useless for many scenarios it > was meant for. I'm not sure I understand. Are you implying that it is somehow possible to circumvent the second (fatal) error with this change? How? --=20 troels