I've bumped the lighttpd 1.3.5 ebuild to 1.3.7 and wrote a new init script and fixed the patch which enables fastcgi for php-cgi. I also "cleaned and updated" the ebuild. Reproducible: Always Steps to Reproduce:
Created attachment 47533 [details] the ebuild
Created attachment 47535 [details] new init script
Created attachment 47536 [details, diff] updated patch for php support
I created an ebuild based in this bug, with the following changes: * changed URI from http://jan.kneschke.de/projects/lighttpd/ to http://www.lighttpd.net * moved spawn-fcgi into lighttpd ebuild (as lighttpd did with 1.3.6: http://www.lighttpd.net/download/NEWS.html), removed spawn-fcgi dependency, added spawn-fcgi.conf and spawn-fcgi.initd to files/ * create a lighttpd usergroup, not only lighttpd user * changed value of "server.username" and "server.groupname" to "lighttpd" in lighttpd.conf (so lighttpd runs under its own user:group) * changed SPAWNFCGI to "/usr/bin/spawn-fcgi" and GROUPID to "lighttpd" in spawn-fcgi.conf (so php-cgi runs unter its own user:group, too) * added ipv6 USE-flag a listing of lighttpd/files/: digest-lighttpd-1.3.7 lighttpd-1.1.8-gentoo.diff (from old ebuild) lighttpd-1.3.7-php.patch (from this bug-report) lighttpd-1.3.7.initd (from this bug-report) spawn-fcgi-1.3.7.conf (from spawn-fcgi ebuild, file attatched) spawn-fcgi-1.3.7.initd (from spawn-fcgi ebuild, file attatched) only spawn-fcgi-1.3.7.conf was changed as mentioned above.
Created attachment 47839 [details] lighttpd-1.3.7.ebuild
Created attachment 47840 [details] spawn-fcgi-1.3.7.conf
Created attachment 47841 [details] spawn-fcgi-1.3.7.initd
Andreas, why do you want to move spawn-fcgi into lighttpd instead of just letting lighttpd depend on spawn-fcgi? If you really need to change spawn-fcgi configuration file(s) then you can easily do this in the lighttpd ebuild.
because the lighttpd author does the same with release 1.3.6: http://www.lighttpd.net/download/NEWS.html Or do you find a link to spawn-fcgi on http://www.lighttpd.net/download/ , yet?
Oh, didn't notice that. But then, shouldn't lighttpd ebuild block spawn-fcgi because obviously it contains the same functionality and both can't work together ?
I'm not an experienced ebuild-developer ;-) The ebuild I created works for me, if you have any ideas to improve it change it! One Problem I have: /etc/init.d/lighttpd starts /etc/init.d/spawn-fcgi, but if I stop /etc/init.d/lighttpd, /etc/init.d/spawn-fcgi does not stop. Or do you have an idea how to bind the fcgi-processes (php-cgi) to a specifc IP? And php-cgi should be compiled with --enable-discard-path --enable-force-cgi-redirect as descriped in lighttpd-docs([1]) and security-chapter of the php-manual ([2], [3]) [1]: http://www.lighttpd.net/documentation/fastcgi.html#preparing-php-as-a-fastcgi-program [2]: http://www.php.net/manual/en/security.cgi-bin.php#security.cgi-bin.attacks [3]: http://www.php.net/manual/en/configure.php#configure.enable-discard-path
1.3.10 is in CVS. Please test, especially the PHP and spawn-fcgi stuff, as that is an area I'm not as experienced in. Btw, Tarmo, *PLEASE* make sure files you attach are in a unix file format, *not* DOS (uses \r\n instead of \n for EOL). I spent an hour or two last night trying to figure out why depscan.sh was going crazy last night and my entire init system was borked ;)
Aaron, the init script I submitted does not contain any CRLF, but the ones submitted by Andres do ;)
I'm sorry, my fault. I did not think about it, I will change this in future.
