https://redmine.lighttpd.net/https://redmine.lighttpd.net/favicon.ico?13667327412008-02-26T23:46:10Zlighty labsLighttpd - Bug #1575: net.inet.tcp.blackhole and spawn-fcgihttps://redmine.lighttpd.net/issues/1575?journal_id=38562008-02-26T23:46:10Zstbuehler
<ul></ul><p>Did you try what happens if you start spawn-fcgi a second time?</p>
<p>I think it will delete the first socket (unlink in the source), and create a new one - and then you have 2 fcgi processes running, but the first one is unreachable as its socket is deleted (but not closed); check by killing the second one (with all childs) and try connecting to it (e.g. with the original spawn-fcgi). (Tested on my linux box)</p>
<p>Please give feedback how FreeBSD behaves ;-)</p> Lighttpd - Bug #1575: net.inet.tcp.blackhole and spawn-fcgihttps://redmine.lighttpd.net/issues/1575?journal_id=38572008-02-27T15:52:21ZAnonymous
<ul></ul><p>When I start the second instance of the unpatched spawn-fcgi it gives me:<br />spawn-fcgi.c.224: socket is already used, can't spawn<br />and exits.</p>
<p>With the patch applied it gives me:<br />spawn-fcgi.c.118: bind failed: Address already in use<br />and exits.</p>
<p>-- tofig</p> Lighttpd - Bug #1575: net.inet.tcp.blackhole and spawn-fcgihttps://redmine.lighttpd.net/issues/1575?journal_id=38582008-02-28T09:56:32Zadmin
<ul></ul><p>You're using IP sockets, while stbuehler is talking about Unix sockets.</p> Lighttpd - Bug #1575: net.inet.tcp.blackhole and spawn-fcgihttps://redmine.lighttpd.net/issues/1575?journal_id=38592008-02-28T11:46:36Zstbuehler
<ul></ul><p>Oh... hehe. Should have seen the "tcp" in "net.inet.tcp.blackhole", sry.</p> Lighttpd - Bug #1575: net.inet.tcp.blackhole and spawn-fcgihttps://redmine.lighttpd.net/issues/1575?journal_id=38602008-02-28T12:19:53Zstbuehler
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Fixed</i></li><li><strong>Resolution</strong> set to <i>fixed</i></li></ul><p>Fixed in r2106</p>