After a short discussion with Rasmus and Johannes (how's maintaining PHP 5.3 branch) it was agreed that FPM can't break anything serious and even though 5.3 is a bugfix branch, it's safe to add FPM there.
Which was done several minutes ago.
So now you don't have to checkout PHP trunk, copy sapi/fpm to your 5.3 source tree and so on - it's all there already. Snapshots containing FPM will be ready in ~1 hour, according to http://snaps.php.net. Feel free to test them and report any issues you find using the official bug tracker @ http://bugs.php.net.
On Wed, May 26, 2010 at 8:29 AM, Antony Dovgal <t...@daylessday.org> wrote: > Hello all.
> After a short discussion with Rasmus and Johannes (how's maintaining PHP 5.3 branch) it was agreed that FPM > can't break anything serious and even though 5.3 is a bugfix branch, it's safe to add FPM there.
> Which was done several minutes ago.
> So now you don't have to checkout PHP trunk, copy sapi/fpm to your 5.3 source tree and so on - it's all there already. > Snapshots containing FPM will be ready in ~1 hour, according to http://snaps.php.net. > Feel free to test them and report any issues you find using the official bug tracker @ http://bugs.php.net.
On Wed, May 26, 2010 at 11:29 AM, Antony Dovgal <t...@daylessday.org> wrote: > Hello all.
> After a short discussion with Rasmus and Johannes (how's maintaining PHP > 5.3 branch) it was agreed that FPM > can't break anything serious and even though 5.3 is a bugfix branch, it's > safe to add FPM there.
> Which was done several minutes ago.
> So now you don't have to checkout PHP trunk, copy sapi/fpm to your 5.3 > source tree and so on - it's all there already. > Snapshots containing FPM will be ready in ~1 hour, according to > http://snaps.php.net. > Feel free to test them and report any issues you find using the official > bug tracker @ http://bugs.php.net.
On Wed, May 26, 2010 at 11:29 AM, Antony Dovgal <t...@daylessday.org> wrote: > Hello all.
> After a short discussion with Rasmus and Johannes (how's maintaining PHP > 5.3 branch) it was agreed that FPM > can't break anything serious and even though 5.3 is a bugfix branch, it's > safe to add FPM there.
> Which was done several minutes ago.
> So now you don't have to checkout PHP trunk, copy sapi/fpm to your 5.3 > source tree and so on - it's all there already. > Snapshots containing FPM will be ready in ~1 hour, according to > http://snaps.php.net. > Feel free to test them and report any issues you find using the official > bug tracker @ http://bugs.php.net.
On Wed, May 26, 2010 at 9:35 PM, Khazret Sapenov <sape...@gmail.com> wrote: > thanks, Anthony! good job.
> On Wed, May 26, 2010 at 11:29 AM, Antony Dovgal <t...@daylessday.org>wrote:
>> Hello all.
>> After a short discussion with Rasmus and Johannes (how's maintaining PHP >> 5.3 branch) it was agreed that FPM >> can't break anything serious and even though 5.3 is a bugfix branch, it's >> safe to add FPM there.
>> Which was done several minutes ago.
>> So now you don't have to checkout PHP trunk, copy sapi/fpm to your 5.3 >> source tree and so on - it's all there already. >> Snapshots containing FPM will be ready in ~1 hour, according to >> http://snaps.php.net. >> Feel free to test them and report any issues you find using the official >> bug tracker @ http://bugs.php.net.
On Wed, May 26, 2010 at 7:29 PM, Antony Dovgal <t...@daylessday.org> wrote: > Hello all.
> After a short discussion with Rasmus and Johannes (how's maintaining PHP 5.3 branch) it was agreed that FPM > can't break anything serious and even though 5.3 is a bugfix branch, it's safe to add FPM there.
> Which was done several minutes ago.
> So now you don't have to checkout PHP trunk, copy sapi/fpm to your 5.3 source tree and so on - it's all there already. > Snapshots containing FPM will be ready in ~1 hour, according to http://snaps.php.net. > Feel free to test them and report any issues you find using the official bug tracker @ http://bugs.php.net.
I just saw the announcement of the FPM being included in PHP 5.3.3.
That's great news - it sounds like the new FPM is a very good one. But
I'd appreciate some clarification on the status of the old FPM in php-
cgi.
The regular php-cgi binaries in 5.2.x and, in my experience, 5.3.0
through 5.3.2 already include the capability of running as a FastCGI
process manager (that is, managing multiple processes themselves). And
this provides the essential feature of a shared APC cache.
Also it sounds like the new SAPI has a separate binary, unlike the old
FPM support which looked for environment variables and altered the
behavior of php-cgi.
So my questions are:
1. Was the old FPM removed from php-cgi in 5.3.3?
2. If so, wouldn't this cause considerable disruption for those of us
who are using it if we upgrade to 5.3.3? If so, documentation of what
to do in order to transition between the FPMs would be very useful.
3. Does the new FPM provide shared APC cache as the old one did? That
feature is a lifesaver for object oriented code on a modest virtual
machine.
I have a widely forwarded article here which I'll update with the
answers once I have them:
> After a short discussion with Rasmus and Johannes (how's maintaining PHP 5.3 branch) it was agreed that FPM
> can't break anything serious and even though 5.3 is a bugfix branch, it's safe to add FPM there.
> Which was done several minutes ago.
> So now you don't have to checkout PHP trunk, copy sapi/fpm to your 5.3 source tree and so on - it's all there already.
> Snapshots containing FPM will be ready in ~1 hour, according tohttp://snaps.php.net.
> Feel free to test them and report any issues you find using the official bug tracker @http://bugs.php.net.
Tom, I have used your very handy article for PHP setups in the past
for Apache2+PHP-FCGI - I'm sure if apache2 can run using the new php-
fpm it will makes things all that little more sweeter.
On Jul 24, 8:21 am, Tom Boutell <t...@punkave.com> wrote:
> I just saw the announcement of the FPM being included in PHP 5.3.3.
> That's great news - it sounds like the new FPM is a very good one. But
> I'd appreciate some clarification on the status of the old FPM in php-
> cgi.
> The regular php-cgi binaries in 5.2.x and, in my experience, 5.3.0
> through 5.3.2 already include the capability of running as a FastCGI
> process manager (that is, managing multiple processes themselves). And
> this provides the essential feature of a shared APC cache.
> Also it sounds like the new SAPI has a separate binary, unlike the old
> FPM support which looked for environment variables and altered the
> behavior of php-cgi.
> So my questions are:
> 1. Was the old FPM removed from php-cgi in 5.3.3?
> 2. If so, wouldn't this cause considerable disruption for those of us
> who are using it if we upgrade to 5.3.3? If so, documentation of what
> to do in order to transition between the FPMs would be very useful.
> 3. Does the new FPM provide shared APC cache as the old one did? That
> feature is a lifesaver for object oriented code on a modest virtual
> machine.
> I have a widely forwarded article here which I'll update with the
> answers once I have them:
> On May 26, 11:29 am, Antony Dovgal <t...@daylessday.org> wrote:
> > Hello all.
> > After a short discussion with Rasmus and Johannes (how's maintaining PHP 5.3 branch) it was agreed that FPM
> > can't break anything serious and even though 5.3 is a bugfix branch, it's safe to add FPM there.
> > Which was done several minutes ago.
> > So now you don't have to checkout PHP trunk, copy sapi/fpm to your 5.3 source tree and so on - it's all there already.
> > Snapshots containing FPM will be ready in ~1 hour, according tohttp://snaps.php.net.
> > Feel free to test them and report any issues you find using the official bug tracker @http://bugs.php.net.
> 1. Was the old FPM removed from php-cgi in 5.3.3?
> 2. If so, wouldn't this cause considerable disruption for those of us > who are using it if we upgrade to 5.3.3? If so, documentation of what > to do in order to transition between the FPMs would be very useful.
> 3. Does the new FPM provide shared APC cache as the old one did? That > feature is a lifesaver for object oriented code on a modest virtual > machine.
1. php-cgi is unchanged and works as before. 2. see number 1. 3. yes, shared apc cache works with php-fpm.
Thanks for the clarification, Brian. So the rudimentary FPM in php-cgi, including support for PHP_FCGI_CHILDREN, is exactly as it was before but the FPM SAPI is a separate and superior implementation for those who are ready to tackle it. Now it's incumbent on all of us to spread the word of this even better option and encourage our friendly distribution vendor to offer an apt/rpm/port etc. that installs it when they move to PHP 5.3.3.
I'm excited about the slow log feature, as well as the improved logging in general.
What does "accelerated upload support" mean in practice?
fastcgi_finish_request() looks useful too.
I don't need the alternate uid/gid stuff but I know hosts who definitely will be excited about it.
On Fri, Jul 23, 2010 at 8:35 PM, Brian Mercer <m...@brianmercer.com> wrote: > On 7/23/2010 6:21 PM, Tom Boutell wrote: >> So my questions are:
>> 1. Was the old FPM removed from php-cgi in 5.3.3?
>> 2. If so, wouldn't this cause considerable disruption for those of us >> who are using it if we upgrade to 5.3.3? If so, documentation of what >> to do in order to transition between the FPMs would be very useful.
>> 3. Does the new FPM provide shared APC cache as the old one did? That >> feature is a lifesaver for object oriented code on a modest virtual >> machine.
> 1. php-cgi is unchanged and works as before. > 2. see number 1. > 3. yes, shared apc cache works with php-fpm.
I have a small question though: I have installed php 5.3.3 through a yum install (remi) but php-fpm does not seemed to be enabled. How can I enable it after an rpm install? Thanks
> I have a small question though: > I have installed php 5.3.3 through a yum install (remi) > but php-fpm does not seemed to be enabled. > How can I enable it after an rpm install? Thanks
if the package manager did not enable FPM before compilation you just can't. It's not like an pecl extension.
You'll have to ask the pkg manager to produce a new version or to compile FPM by yourself.
> I have a small question though: > I have installed php 5.3.3 through a yum install (remi) > but php-fpm does not seemed to be enabled. > How can I enable it after an rpm install? Thanks
It's quite stable, at least for me. The russian guy is recompiling remi packages with php-fpm enable. Be aware with other packages in repository like bind, openssh and others, maybe you don't want to upgrade these ones.
