Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] IMAP server restart causes Sup exception
Date: Tue, 20 May 2008 16:03:08 +0100	[thread overview]
Message-ID: <1211295759-sup-614@tomsk> (raw)
In-Reply-To: <1211238704-sup-2539@south>

On 20.5.2008, William Morgan wrote:
> > closed stream
> > /usr/lib/ruby/1.8/openssl/buffering.rb:237:in `select'
> > ./lib/sup/buffer.rb:31:in `nonblocking_getch'
> > bin/sup:227
> 
> This backtrace doesn't really make any sense. There's no reason that
> nonblocking_getch would be calling the openssl stuff, and openssl's
> buffering.rb doesn't mention select at all. Weird.

I should pipe up here as well - this exception was one of the reasons
I switched to offlineimap as I would get it randomly in sup during
imap actions. I couldnt figure out how they interacted with each other
though as it didnt happen enough to debug :(

Marcus


  reply	other threads:[~2008-05-20 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  1:23 Kevin Riggle
2008-05-19 23:16 ` William Morgan
2008-05-20 15:03   ` Marcus Williams [this message]
2008-05-20 16:05     ` William Morgan
2008-05-20 16:23       ` Ben Walton
2008-05-25  2:45         ` William Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1211295759-sup-614@tomsk \
    --to=marcus-sup@bar-coded.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox