ID: 45049
User updated by: szoftos at freemail dot hu
Reported By: szoftos at freemail dot hu
-Status: Feedback
+Status: Open
Bug Type: CGI related
Operating System: FreeBSD
PHP Version: 5.2.6
New Comment:
Hello,
original configuration snippet follows:
$HTTP["host"] =~ "^crxforum\.flix\.hu$|^crxforum\.localhost$" {
server.document-root =
"/var/www/crxforum.flix.hu/crxforum.flix.hu"
fastcgi.server = ( ".php" =>
((
"socket" => "/tmp/crxforum.flix.hu.php.sock",
"broken-scriptfilename" => "enable",
))
)
accesslog.filename =
"/var/log/lighttpd/crxforum.flix.hu-access.log"
server.errorlog = "/var/log/lighttpd/crxforum.flix.hu-error.log"
server.error-handler-404 = "/404.php"
$HTTP["url"] =~ "^(/images/|/skins/|/js/)" {
expire.url = ( "" => "access 1 years" )
}
}
Previous Comments:
------------------------------------------------------------------------
[2008-05-22 08:42:34] [EMAIL PROTECTED]
Please provide the actual fastcgi.server part of your lighttpd.conf.
Also, how did you compile/configure PHP itself? (OTOH, *bsd has lot of
problems dealing with symlinks, just search this bug db..:)
------------------------------------------------------------------------
[2008-05-20 09:37:40] szoftos at freemail dot hu
Description:
------------
Hello,
recently i changed my operating system from linux to freebsd, which has
its default documentroot in /usr/local/www, and linux had it in
/var/www. i moved my files to /usr/local/www, but i made a symlink into
/var:
'cd /var'
'ln -s ../usr/local/www www'
lighttpd has its old configs, locating files in /var/www, but this
shouldn't be a problem with the symlink.
php got its settings locating files in /usr/local/www, and i got
sometimes a mystical response from the fcgi-php: 'No input file
specified.'
i lowered the spawned processes to 2 (sadly i couldn't lower it to 1),
and traced one of the two processes. one of them was the faulty, and i
had luck: i have seen that lighttpd passed /var/www (normally) to
php-fcgi, and somehow php-fcgi couldn't really resolve the symlink.
the problem solved when i changed /var/www to /usr/local/www in
lighty's configuration.
this looks like a problem to me, and it is not unique. i had this
situation with one of my other virtualhosts too. the spawned processes
are resolving that symlink good in most of the time, but then one
process stops resolving it right, and produces the message, as i have
written.
this should be a problem.
i have gone to lighttpd developers, and they told me its a php problem.
the original bugreport is here:
http://trac.lighttpd.net/trac/ticket/1668
Reproduce code:
---------------
You can reproduce if you use the same settings as i mentioned above.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=45049&edit=1
