Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47626 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96603 invoked from network); 25 Mar 2010 22:17:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Mar 2010 22:17:28 -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 74.125.82.42 cause and error) X-PHP-List-Original-Sender: jerome@loyet.net X-Host-Fingerprint: 74.125.82.42 mail-ww0-f42.google.com Received: from [74.125.82.42] ([74.125.82.42:64194] helo=mail-ww0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 15/21-25388-6F0EBAB4 for ; Thu, 25 Mar 2010 17:17:27 -0500 Received: by wwc33 with SMTP id 33so2103310wwc.29 for ; Thu, 25 Mar 2010 15:17:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.93.79 with SMTP id k57mr675470wef.161.1269555443469; Thu, 25 Mar 2010 15:17:23 -0700 (PDT) In-Reply-To: References: <4BA8EF6F.8010503@daylessday.org> <7.0.1.0.2.20100324000837.13ff3080@zend.com> <4BA9CB98.6080102@daylessday.org> <7.0.1.0.2.20100324102437.0b491a68@zend.com> <4BA9D167.30006@daylessday.org> <99cf22521003240334y6fb76fbcs4347429f3be48d49@mail.gmail.com> <3bea96c41003250709jd391239te35ab88b46e4803e@mail.gmail.com> <99cf22521003251453k4a9a5d4n5b7522f0c677d037@mail.gmail.com> Date: Thu, 25 Mar 2010 23:17:23 +0100 Message-ID: <3bea96c41003251517v5a9abf78udfb4ffe2a9788688@mail.gmail.com> To: Michael Shadle Cc: dreamcat four , php-dev Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] FPM RFC From: jerome@loyet.net (=?ISO-8859-1?B?Suly9G1lIExveWV0?=) 2010/3/25 Michael Shadle : > 2010/3/25 dreamcat four : > >> If you intend to implement this Jerome, then perhaps (any time when / >> after you implement), just make new (seperate) RFC for that (just the >> ini). Which (obviously) can be attached as single dependancy of this >> RFC. That way, those comments / feedback can come directed back for >> just you (on your chosen, preferred ini implementation). And we don't >> get confused over the other ini examples. > > I agree this does look decent and supports includes (/me is happy) > > One thing - can the main fpm.conf be defined in php.ini? Instead of at > compile time? > Is there any sapi with directives in php.ini ? I can't see any reasons to have some FPM specifics into php.ini. To change the default conf file, juste specified it in the commande line like any other daemon you have running on your boxes.