From: Tatsuki Sugiura <[EMAIL PROTECTED]> Subject: Re: Bug#298819: libapache2-mod-fastcgi: insufficient settings in fastcgi.conf Date: Thu, 10 Mar 2005 17:25:00 +0900
> O.K..., You need below to run FastCGI Script; > > * Load mod_fastcgi.so. Restart apache and check your error.log, > "[notice] FastCGI: process manager initialized (pid 14145)" > when mod_fastcgi load success. If you can not find the line, > run a2enmod to enable fastcgi. Yes, I did run a2enmod. To run a2enmod is described in /etc/apache2/README. > * Permission for running "CGI" in the directory, using > - Options +ExecCGI > or > - ScriptAlias > * The script was handled as "fastcgi-script". If you do not > use ".fcgi" suffix, specify AddHandler (or SetHandler). > e.g., "AddHandler fastcgi-script .yourext" Yes, I lerned these kind of info in http://www.fastcgi.com/docs/faq.html#typical_httpd.conf and in fact I succeeded to run a fastcgi script. But, my main point is why these settings were not provided in fastcgi.conf by default? With the current state, a user should modify fastcgi.conf when one needs to use a fastcgi script really...? Is there any problem I missed to provide these settings in fastcgi.conf? Even so, I guess it would be good to provide these settings as comments in fastcgi.conf. BTW, when one wants to package an appli with fastcgi script(s) the current fastcgi.conf is not good because a package can't modify a conffile. Thanks, 2005-3-10(Thu) -- Debian Developer & Debian JP Developer - much more I18N of Debian Atsuhito Kohda <[EMAIL PROTECTED]> Department of Math., Univ. of Tokushima -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
