James, It is happening to me, and I'm pretty sure I've not got a pthread-enabled binary. At any rate, I added track_eof = false just before releasing cap2, so it should all be good.
- Jamis On 7/24/07, James Edward Gray II <[EMAIL PROTECTED]> wrote: > > On Jul 21, 3:30 pm, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > > Thanks David, I can duplicate it now with that sequence of commands. > > I'll investigate and see what I can find out. > > This is a known issue for some installs of Ruby. I believe it only > affects Ruby installs compiled with --enable-pthread. Using such an > install can change the return value of some IO methods called after a > thread has run. There are more details about this problem at: > > http://groups.google.com/group/comp.lang.ruby/browse_thread/thread/939d9f86a18e6f9e/ec1c3f1921cd66ea?lnk=gst&q=STDIN+EOF+James+Edward+Gray+II&rnum=1#ec1c3f1921cd66ea > > HighLine includes a workaround for this, which is to set track_eof to > false: > > HighLine.track_eof = false > > I recommend Capistrano make this call when it loads HighLine because > the networking libraries use threads and this is likely to affect many > users. > > Hope this helps. > > James Edward Gray II > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
