Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#19499 - [php-cgi] Distribute a fastcgi daemon with it

Attached to Project: Arch Linux
Opened by ux (ubitux) - Monday, 17 May 2010, 16:02 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 03 July 2010, 19:31 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Each time we install a web server like nginx, we need to make a home-made fastcgi service (https://wiki.archlinux.org/index.php/Nginx#Use_PHP.2FPython_with_nginx). In my mind, as php-cgi package delivers a daemon, it should be accompanied with the /etc/rc.d/phpfastcgi daemon script to avoid the archaic script copy/paste from wiki/blogs/IRC/whatever.

Regards.
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Saturday, 03 July 2010, 19:31 GMT
Reason for closing:  Won't implement
Comment by Jan de Groot (JGC) - Monday, 17 May 2010, 21:38 GMT
This is all up to the user. For the hosting of archlinux.org we have .fcgi scripts that are started dynamic by mod_fcgid or mod_fastcgi. For many setups there's no need to use the standalone daemon method.
Comment by ux (ubitux) - Tuesday, 18 May 2010, 05:55 GMT
NGinx is a really common server, and I don't know any other way to do that. A 30 lines rc.d script won't burden the package, and won't ever be started automatically. Using it and adding it to DAEMONS list *is* all up to the user, no?

A lot of packages contains daemons we'll never use (subversion when used as a client, rsyncd, …), why being to reluctant to add this one?
Comment by Jan de Groot (JGC) - Tuesday, 18 May 2010, 13:57 GMT
The point is that we could add an additional init script, but next thing will be:
- which port to run it on
- what environment variables to start it with
- what optional commandline params to start it with
- what user to run it with
- maybe you would like to have a php-fcgi instance per vhost or even per script

As you'll have to customize these things yourself, I don't see the need to add an init script to the php-cgi package.
Comment by Pierre Schmitz (Pierre) - Saturday, 03 July 2010, 19:31 GMT
There is spawn-fcgi for this. And with PHP 5.3.3 we'll have php-fpm. For php-cgi itself this is more a web server configuration issue.

Loading...