Upstream closed connection...
kupokomapa at gmail.com
Wed Sep 24 11:22:51 MSD 2008
The best exposure would be to get included finally into PHP core and
then it will be readily available, but until then, keep on doing the
advertising campaign :)
On Tue, Sep 23, 2008 at 11:02 PM, mike <mike503 at gmail.com> wrote:
> Quite the opposite! I actually offered to pay him to help expedite things :)
> It simply is the best way to manage php under fastcgi. I had an idea that
> kind of resembled php-fpm, and while asking around for someone to make it, I
> was pointed to php-fpm. I had never heard or known about it. Not enough
> As I don't know C I'm doing my best to help the project... Which is getting
> exposure and getting the name out there. :)
> On Sep 23, 2008, at 12:06 PM, "Kiril Angov" <kupokomapa at gmail.com> wrote:
>> Mike, you are getting paid by Andrei, right :)
>> On Tue, Sep 23, 2008 at 9:06 PM, mike <mike503 at gmail.com> wrote:
>>> I could have told you that :)
>>> On Sep 23, 2008, at 10:42 AM, Gen Gennix <lists at ruby-forum.com> wrote:
>>>> I didn't find the origin of my "upstream prematurely closed connection
>>>> while reading response header from upstream" error, but since I changed
>>>> spawn-fcgi to php-fpm, there is no more error.
>>>> So, today, the lesson is "use php-fpm" (http://php-fpm.anight.org/)
>>>> Posted via http://www.ruby-forum.com/.
More information about the nginx