I glanced over at sup and saw this instead. It was sprawled out over the screen in the way curses apps do when they output stuff via stdout/stderr. No sup-exception.txt seemed to be generated.
/usr/lib/ruby/1.8/net/imap.rb:932:in `close': closed stream (IOError) from /usr/lib/ruby/1.8/net/imap.rb:932:in `receive_responses' from /usr/lib/ruby/1.8/net/imap.rb:923:in `initialize' from /usr/lib/ruby/1.8/net/imap.rb:922:in `start' from /usr/lib/ruby/1.8/net/imap.rb:922:in `initialize' from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:221:in `new' from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:221:in `unsafe_connect' from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:218:in `initialize' from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:218:in `new' ... 15 levels... from /var/lib/gems/1.8/gems/sup-0.3/bin/sup:174:in `each' from /var/lib/gems/1.8/gems/sup-0.3/bin/sup:174 from /var/lib/gems/1.8/bin/sup:16:in `load' from /var/lib/gems/1.8/bin/sup:16 /usr/lib/ruby/1.8/net/imap.rb:932:in `close': closed stream (IOError) from /usr/lib/ruby/1.8/net/imap.rb:932:in `receive_responses' from /usr/lib/ruby/1.8/net/imap.rb:923:in `initialize' from /usr/lib/ruby/1.8/net/imap.rb:922:in `start' from /usr/lib/ruby/1.8/net/imap.rb:922:in `initialize' from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:221:in `new' from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:221:in `unsafe_connect' from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:218:in `initialize' from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:218:in `new' ... 15 levels... from /var/lib/gems/1.8/gems/sup-0.3/bin/sup:174:in `each' from /var/lib/gems/1.8/gems/sup-0.3/bin/sup:174 from /var/lib/gems/1.8/bin/sup:16:in `load' from /var/lib/gems/1.8/bin/sup:16 -- Ian Taylor _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
