On Mon, 11 Jun 2007, David Favor wrote:
1) async appears to start correctly and work correctly when no -j given
OK.
2) when starting async incorrectly senses how Danga::Socket will poll, which should access Danga::Socket->method()
Yup. That's minor, but easily fixed. It doesn't affect the running.
3) when started with '-j 2' errors tumble out, both processes appear to start and messages appear to cycle between the two pids (with a mass of error messages) and deliver correctly.
Very odd. All I can say is "works for me" :-( I'll try and dig into it though.
4) when '-j 2' supplied CNTL-C on command line leaves both processes running.
Again, this works for me... I suspect it's some weird signal handling issue. I really hate this sort of thing :-)
Matt.
