Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: kevinr@mit.edu (Kevin Riggle)
Subject: [sup-talk] IMAP server restart causes Sup exception
Date: Tue, 13 May 2008 21:23:58 -0400	[thread overview]
Message-ID: <1210728028-sup-3439@black-opal> (raw)

Restarting my IMAP server caused the following Sup exception.

--- SystemExit from thread: main
closed stream
/usr/lib/ruby/1.8/openssl/buffering.rb:237:in `select'
./lib/sup/buffer.rb:31:in `nonblocking_getch'
bin/sup:227

Sup should really handle this more gracefully.

- Kevin
-- 
Kevin Riggle (kevinr at mit.edu) 
http://free-dissociation.com


             reply	other threads:[~2008-05-14  1:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  1:23 Kevin Riggle [this message]
2008-05-19 23:16 ` William Morgan
2008-05-20 15:03   ` Marcus Williams
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=1210728028-sup-3439@black-opal \
    --to=kevinr@mit.edu \
    /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