FastCgiIpcDir already defined
Bill Moseley <[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <[email protected]> |
On Debian with Apache 1.3x mod_fastcgi creates: $ cat conf.d/fastcgi.conf <IfModule mod_fastcgi.c> AddHandler fastcgi-script .fcgi #FastCgiWrapper /usr/lib/apache/suexec FastCgiIpcDir /var/lib/apache/fastcgi </IfModule> And the httpd.conf file loads those conf.d config at the end of httpd.conf. Now, if I try and enable a static application with FastCGIServer in httpd.conf I see: Syntax error on line 4 of /etc/apache/conf.d/fastcgi.conf: FastCgiIpcDir /var/lib/apache/fastcgi: already defined as "/etc/apache/logs/fastcgi" failed! Does using FastCGIServer implicitly set FastCgiIpcDir? I realize I can just place FastCGIServer later in my config. By the way, I've spent a while reading over the docs, but still somewhat unclear about how the process manager fits into things. Are there docs somewhere that give a general overview of the manager and how it fits in with Apache and the application? A few very basic questions that I'm still not clear on: For example, does using FastCGIServer tell the process manager to start the application process (or processes) and maintain a pool of connections? Does Apache connect to the process manager or directly to the applications? Are the connections kept open or are the created for each request? Thanks, -- Bill Moseley [email protected] ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/