spawn-fcgi sometimes cannot resolve symlinks
recently i changed my operadting 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:
'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.
Also available in: Atom