https://redmine.lighttpd.net/https://redmine.lighttpd.net/favicon.ico?13667327412007-11-06T19:08:18Zlighty labsLighttpd - Bug #1435: fcgi spawn or chroot mistiminghttps://redmine.lighttpd.net/issues/1435?journal_id=35132007-11-06T19:08:18ZAnonymous
<ul></ul><p>(wanted to add my email address)</p>
<p>-- tech</p> Lighttpd - Bug #1435: fcgi spawn or chroot mistiminghttps://redmine.lighttpd.net/issues/1435?journal_id=35142007-11-06T21:55:27Zjrabbit
<ul></ul><p>Version 1.5.0 no longer spawns PHP - it only connects to an independent PHP fastcgi server. You can use the spawn-fcgi program that comes with lighttpd to launch a copy of PHP that lighttpd will connect to.</p> Lighttpd - Bug #1435: fcgi spawn or chroot mistiminghttps://redmine.lighttpd.net/issues/1435?journal_id=35152007-11-06T22:17:42ZAnonymous
<ul></ul><p>Replying to <a class="wiki-page new" href="https://redmine.lighttpd.net/projects/lighttpd/wiki/Comment2">jrabbit</a>:</p>
<blockquote>
<p>Version 1.5.0 no longer spawns PHP - it only connects to an independent PHP fastcgi server. You can use the spawn-fcgi program that comes with lighttpd to launch a copy of PHP that lighttpd will connect to.</p>
</blockquote>
<p>Does this also refer to 1.4.18? Perhaps I misphrased the situation: somehow a fastcgi php is getting invoked (creating sockets in /tmp). Lighttpd is supposed to be running chroot in /jaildir. There are not sockets in /jaildir/tmp. Somehow the lighttpd that is supposed to be chrooted into /jaildir is able to communicate to these sockets in /tmp (I'm guessing this is how lighttpd talks to a fastcgi php) What could be causing this?</p>
<p>I haven't explicitly started anything php ever and I wrote the startup files for the server, so I don't understand how a fastcgi server would already be running. Some more information:</p>
<p>I have two jails:<br />/opt/kwur/externalroot<br />/opt/kwur/internalroot</p>
<p>Each jail has its own PHP-5.2.4 and lighttpd that was --prefix'd into that directory. Each jail has the appropriate libs as determined by ldd. There is also a global PHP 5.2.4 that I use for running scripts installed into /usr/local, and it is this PHP that would have access to /tmp and it seems that it is this PHP that lighttpd is managing to start when it should not be able to.</p> Lighttpd - Bug #1435: fcgi spawn or chroot mistiminghttps://redmine.lighttpd.net/issues/1435?journal_id=35162007-11-07T00:46:42Zjrabbit
<ul></ul><p>Sorry - I saw milestone 1.5.0 and mistook it for the version. However, I used to use the spawn-fcgi script in 1.4 as well even, though it was optional in that version and lighttpd could spawn its own php. Using the external service gives you a way to ensure the php fastcgi service runs inside the jail. It also means you can restart it independently of lighttpd.</p> Lighttpd - Bug #1435: fcgi spawn or chroot mistiminghttps://redmine.lighttpd.net/issues/1435?journal_id=35172007-11-11T06:15:29ZAnonymous
<ul></ul><p>You can close this! netstat lists /tmp/whatever but it is mistaken, the sockets do reside in the proper jail! No problems, sorry for troubling all of you!</p> Lighttpd - Bug #1435: fcgi spawn or chroot mistiminghttps://redmine.lighttpd.net/issues/1435?journal_id=35182007-11-11T18:45:12Zdarix
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Fixed</i></li><li><strong>Resolution</strong> set to <i>invalid</i></li></ul> Lighttpd - Bug #1435: fcgi spawn or chroot mistiminghttps://redmine.lighttpd.net/issues/1435?journal_id=46452008-10-10T18:54:20Zstbuehler
<ul><li><strong>Status</strong> changed from <i>Fixed</i> to <i>Invalid</i></li></ul>