Reformatted excerpts from Edward Z. Yang's message of 2009-06-03: > The current working theory (based on strace'ing and lsof) is that Sup > is hanging on a select() call that doesn't have any timeout. The > reason why this is hanging is because between opening the connection > and closing it, Sup does some ridiculously slow message parsing code > (that really thrashes the CPU) and by the time it's done the server > has closed the connection (but we don't know about it).
That may all be true, but I'd be surprised if a) Sup didn't know that the server had closed the connection, and b) that this would cause the whole thing to hang. When you don't use -n, does Sup still lock up? -- William <wmorgan-...@masanjin.net> _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
