Bug#482601: lighttpd: Fails to start at all if a FastCGI responder fails

2009-10-10 Thread Stefan Bühler
Hi, if you don't want lighttpd to depend on your fastcgi applications, you should spawn them with supervise(daemontools)/runit + spawn-fcgi (and remove bin- path from the lighty config). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe.

Bug#482601: lighttpd: Fails to start at all if a FastCGI responder fails

2008-05-23 Thread Paul LeoNerd Evans
Package: lighttpd Version: 1.4.19-4 Severity: normal One of my FastCGI responder processes fails to start. This is fine, this is my problem. But this seems to cause the entire lighttpd to start at all, meaning not only that responder, but all of any of my virtual sites cannot function. Surely it