Bug #623
closedmax-procs not handled for local (unix socket) SCGI in mod_scgi
Description
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.
-- Basile STARYNKEVITCH
Files
Updated by Anonymous over 18 years ago
That should fix it in the latest 1.4 branch. I don't know what happened to mod_scgi in the trunk though.
-- milde
Updated by Anonymous over 18 years ago
Also, if someone with power could remove my email from the attachment--which I mistakenly left in--that would be nice.
-- milde
Updated by sjamaan about 17 years ago
Another workaround is to replace min-procs with min-procs-not-working. It will honour that setting as if it were min-procs.
Updated by stbuehler over 16 years ago
- Status changed from New to Fixed
- Resolution set to fixed
Appliend in r2109
Also available in: Atom