Gnus development mailing list
 help / color / mirror / Atom feed
From: John Sullivan <john@wjsullivan.net>
To: ding@gnus.org
Subject: OpenSSL using 100% cpu for connection to localhost imap
Date: Thu, 24 Feb 2011 16:43:23 -0800	[thread overview]
Message-ID: <87ipw9kkpg.fsf@myles.home.wjsullivan.net> (raw)

I just updated from emacs bzr today.

 openssl s_client -connect localhost imaps -no_ssl2 -ign_eof

is using 100% of my CPU and has been for a while. I'm not sure when it
started doing so, but I know that I restarted emacs after updating,
started gnus, entered an nnimap group, read some articles, and sent a
reply.

(BTW, is there a way to connect without encryption? It's localhost on a
single user machine. Looks like setting nnimap-stream to network will
just cause starttls to be selected.)




             reply	other threads:[~2011-02-25  0:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25  0:43 John Sullivan [this message]
2011-02-25  3:56 ` Lars Ingebrigtsen
2011-03-13 20:19   ` John Sullivan
2011-03-13 23:49     ` John Sullivan
2011-03-14 17:00       ` John Sullivan
2011-03-15 15:53         ` Lars Magne Ingebrigtsen
2011-03-15 20:07           ` John Sullivan
2011-03-15 22:20             ` Lars Magne Ingebrigtsen

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=87ipw9kkpg.fsf@myles.home.wjsullivan.net \
    --to=john@wjsullivan.net \
    --cc=ding@gnus.org \
    /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;
as well as URLs for NNTP newsgroup(s).