> Can you suggest any documentation I should read that describes how
> FastCGI handles PIPES and file channels.
The FastCGI spec. should be fine.
> I thought something like that was happening but, if that was the case
> wouldn't the output to stderr and stdout end up in the rendered pages
> (lik
Can you suggest any documentation I should read that describes how
FastCGI handles PIPES and file channels.
I thought something like that was happening but, if that was the case
wouldn't the output to stderr and stdout end up in the rendered pages
(like they do for php pages). I have poked and pr
On Jun 2, 7:12 am, The Code Janitor <[EMAIL PROTECTED]> wrote:
> The problem is that I am loosing [sic] stdout and stderr.
Yes, that's how most FastCGI spawners work. They close all file
descriptors, and open a new socket, then duplicate that socket's FD
onto a constant known as FCGI_LISTENSOCK_F
I am running Django on a centos box using lighttpd and fastcgi. I
found that if I didn't daemonize the fastcgi process and did not
specify a socket name to the manage.py script that the fcgi handlers
cooperated better and was able to place all of the fcgi process under
the control of lighttpd and
