spawn-fcgi-1.6.0rc1-r16 prerelease]

[Grzegorz Nosek]

On nie, mar 08, 2009 at 02:17:17 -0800, mike wrote:
> spawn-fcgi was not properly recycling php engines (i.e.
> PHP_MAX_FCGI_REQUESTS or whatever) when i was using it, i was able to
> validate it. i wound up going back to a custom php -b solution until i
> found php-fpm. so there -are- bugs.

spawn-fcgi doesn't care about php engines, CGI processes and whatnot.
If your bug report contains the word PHP, then it _certainly_ isn't
about spawn-fcgi. There is *never* a single point in time when both
spawn-fcgi and php-fcgi run side by side (one simply becomes the other).

Are you positive you can reproduce a bug using spawn-fcgi and not using
php -b? That would be mildly interesting (another one in the endless
stream of PHP bugs).

> Can Grzegorz get in here and you two can hash out how it works? :)

Trying my best :)

Best regards,
 Grzegorz Nosek