Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47958 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 36265 invoked from network); 15 Apr 2010 08:54:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Apr 2010 08:54:09 -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.219 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.219 mail-bw0-f219.google.com Received: from [209.85.218.219] ([209.85.218.219:48546] helo=mail-bw0-f219.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A7/68-20494-034D6CB4 for ; Thu, 15 Apr 2010 04:54:09 -0400 Received: by bwz19 with SMTP id 19so15982bwz.1 for ; Thu, 15 Apr 2010 01:54:06 -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:received:message-id:subject:from:to:cc:content-type; bh=CJI746HcX0KG4hprPytYgBGdaLkPaT8dD8E6Pe/SlDs=; b=NzCw8B1KDV58S/tqJH+Y3u2tzMcySU/i4xuloWu9geBIvEc3M9ww8ZneDFJCpejs6M GLdz2S4UqAIH26yWbKcjYsZkwLB8b2RyMRw0JNCe294JcnqbLUSRICr9xqeMYOkvxZ04 2BMqFwa5qva/lVxDj3cdWtABpF1p7WeBGAcEA= 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=L0AKCphbF6QX+HypFFiiPoKIMRPKw3TK6cW8zC+Om2IoF+PFAGHbiWeHD2sT30Q1/j VsU/m5GFxHvquVgwlFSk+bCEwUQluH3mkrq7AaI+sY63k6ZXzOIzF7WY4vGlZbTLwQdg xIwisg5zXqOdtf7nzKy3/XewcJsA1POZ/VSeU= MIME-Version: 1.0 Received: by 10.204.123.20 with HTTP; Thu, 15 Apr 2010 01:54:05 -0700 (PDT) In-Reply-To: <4BC6D01C.30407@daylessday.org> References: <4BC6CAE6.5020605@daylessday.org> <4BC6D01C.30407@daylessday.org> Date: Thu, 15 Apr 2010 10:54:05 +0200 Received: by 10.204.81.134 with SMTP id x6mr10022756bkk.32.1271321645945; Thu, 15 Apr 2010 01:54:05 -0700 (PDT) Message-ID: To: Antony Dovgal Cc: =?UTF-8?B?SsOpcsO0bWUgTG95ZXQ=?= , internals@lists.php.net Content-Type: multipart/alternative; boundary=0016e6da9c811a13f6048442a36f Subject: Re: [PHP-DEV] One suggestion to PHP-FPM From: tyra3l@gmail.com (Ferenc Kovacs) --0016e6da9c811a13f6048442a36f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2010/4/15 Antony Dovgal > On 15.04.2010 12:23, J=C3=A9r=C3=B4me Loyet wrote: > > 2010/4/15 Antony Dovgal : > >> On 06.04.2010 11:11, =E6=BB=95=E8=B7=AF=E9=81=A5 wrote: > >>> So I suggest that if we could add a config option to PHP-FPM, so that > >>> PHP-FPM could just kill a PHP process if it consumes too much memory > >>> (say more than 256M). > >> > >> I personally don't think this belongs to any SAPI. > >> How about adding another ini option to PECL/memtrack to not just throw= a > warning, > >> but terminate the process when it hits some limit? > > > > In fork processes it could be great but when dealing with threads it > won't work > > Adding this to FPM won't help anyway - FPM doesn't use threads. > > You meant won't hurt? Tyrael --0016e6da9c811a13f6048442a36f--