Olivier Berger wrote:
Package: sympa
Version: 5.2.3-1.2
Severity: normal
I'm not sure if this is important...
I've run into the situation where I had 'use_fast_cgi' set to 0 in
/etc/sympa/wwsympa.conf and wwsympa.fcgi wouldn't work (running as a simple CGI
instead of using all FastCGI API's resources, which is no
good).
For the records, I though that mod_fastcgi wasn't working since I had
wwsympa.fcgi's output in error.log... see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411928 for some details... and
my misunderstanding of what FastCGI was about ;)
But it was just that use_fast_cgi should have been set to 1 when fastcgi tried
to execute wwsympa.fcgi...
I'm not sure how the variable was set to 0, though.
I'm not completely sure that this situation is linked to this... but still I
think that debconf's FastCGI activation should result in setting use_fast_cgi
accordingly in /etc/sympa/wwsympa.conf ...
There are known problems with mod_fastcgi with Apache 2.2 because the
Apache API has changed. A patch has been provided by a user but it was
not applied back in mod_fastcgi itself. The patch :
http://hack.emilykwan.com/node/95
Since mod_fastcgi seems to be a dead product, it is worth looking at
alternatives :
* mod_fcgid ; see
http://www.sympa.org/wiki/faq/fastcgi?s=fastcgi#installing_mod_fcgid_for_apache2_on_debian
* mod_proxy_fcgi (http://mproxyfcgi.sourceforge.net/) might be
integrated in Apache itself
