Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48084 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 10245 invoked from network); 26 Apr 2010 10:09:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Apr 2010 10:09:01 -0000 Authentication-Results: pb1.pair.com smtp.mail=jerome@loyet.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=jerome@loyet.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain loyet.net from 209.85.218.216 cause and error) X-PHP-List-Original-Sender: jerome@loyet.net X-Host-Fingerprint: 209.85.218.216 mail-bw0-f216.google.com Received: from [209.85.218.216] ([209.85.218.216:62311] helo=mail-bw0-f216.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F2/21-04231-C3665DB4 for ; Mon, 26 Apr 2010 06:09:01 -0400 Received: by bwz8 with SMTP id 8so11694073bwz.23 for ; Mon, 26 Apr 2010 03:08:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.5.140 with SMTP id 12mr2470689bkv.34.1272276537511; Mon, 26 Apr 2010 03:08:57 -0700 (PDT) Received: by 10.204.134.152 with HTTP; Mon, 26 Apr 2010 03:08:57 -0700 (PDT) In-Reply-To: <4BD564A9.2060000@daylessday.org> References: <4BC58D10.4050609@lerdorf.com> <4BD54437.2020304@daylessday.org> <4BD54D42.5070400@daylessday.org> <4BD564A9.2060000@daylessday.org> Date: Mon, 26 Apr 2010 12:08:57 +0200 Message-ID: To: Antony Dovgal Cc: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] One suggestion to PHP-FPM From: jerome@loyet.net (=?ISO-8859-1?B?Suly9G1lIExveWV0?=) Le 26 avril 2010 12:02, Antony Dovgal a =E9crit : > On 26.04.2010 13:38, J=E9r=F4me Loyet wrote: >> I see how adding limits but how can a PECL module can do process >> management (killing) without interfacing with the corresponding SAPI ? > > What exactly are you going to do? > Killing a process is as easy as exit(), no interfacing is needed. and when threads are used ? You'll kill all threads at once without waiting them to finish what they're doing at the time ? I'm asking not to proove something, I'm just asking to go deeper into the subject. > >>> That's why memtrack uses mallinfo(). >> >> mallinfo is not present on every system (mac os, *bsd, ...) > > Hah! I knew you'd say it. > It works fine on FreeBSD 8.0. dammit :))) > > If there is some way to get this info on other systems, we can implement = it in the extension. > If there is no such info available - you can forget about those systems a= nyway, you can't help it. of course > > -- > Wbr, > Antony Dovgal > --- > http://pinba.org - realtime statistics for PHP >