I seriously doubt this. lighty first creates the socket, then tries to spawn the backend, so if the socket creation/bind would fail, it wouldn't event fork.
And i can't imagine that your sudo commands fix anything (even if your /tmp permissions would be broken and not allow lighty to create a socket in it). Use strace on lighty (strace -ff lighttpd -D -f /etc/lighttpd/lighttpd.conf) to see what happens. otoh, i guess this is way too old to find out what really happened. -- Missing socket for FastCGI in Lighttpd https://bugs.launchpad.net/bugs/236105 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
