Thank-you for the tip, Izidor! I appreciate the heads-up. What are the alternatives? Using threads to do polling currently makes Net::SSH really brittle.
I'll be doing some Windows testing before I release, so we'll see if anything comes up at that time. - Jamis On 7/31/07, Izidor Jerebic <[EMAIL PROTECTED]> wrote: > > > On 26.7.2007, at 22:17, Jamis Buck wrote: > > > > > I'm still suspecting Net::SSH, myself, and it's wild and unnecessary > > use of threads. The good news, though, is that Net::SSH v2 is coming > > along nicely, and uses IO.select instead of threads, which it should > > have done all along. > > Jamis, > > From one of my extremely unpleasant (but luckily very rare) > excursions into the beautiful world of microsoft: > > I have never looked into Net:SSH code, but one word of caution about > using select() or its win32 equivalent on windose: there is a well- > known fact that there is a problem with non-blocking pipes and select > () - pipes cannot be used in a non-blocking way and this can lead to > deadlocks. The most famous problem (AFAIK) related to this is cygwin > rsync hanging while using ssh for communication with server (rsync > uses select() for full-duplex I/O). > > Maybe it's nothing, but just so you know... > > izidor > > P.S. I don't care if cap works on windose or not (I avoid MS as much > as I can), so this email is just a public service, sort of :-) > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
