This is actually a mod_scgi bug (no mod_scgi component choice here)
The following configuration does not create, as expected, a single instance of SCGI process:
which I want to run locally (on a very lightly loaded lighttpd server - for debugging & development purposes, I am the only user of the HTTP server). I also would like lighttpd/mod_scgi to start my process (ie the SCGI server) and I want the communication to be done on a Unix socket.
scgi.max-procs = 1
scgi.server = (".bark" => ("localhost" => (
"bin-path" => env.HOME + "/BarkScgi/bark.scgi -d",
"min-procs" => 1,
"max-procs" => 1,
"idle-timeout" => 100,
"socket" => "/var/tmp/bark_scgi_socket"
))
See http://forum.lighttpd.net/topic/657 for more details.
A workaround is known: use TCP/IP communication (thru localhost:4002 for example) and start separately the SCGI server. But this is less practical to me, and I believe that the above configuration is documented to work.
