From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] CPU at 99%
Date: Fri, 31 Oct 2008 16:53:39 -0700 [thread overview]
Message-ID: <1225497126-sup-2054@entry> (raw)
In-Reply-To: <Lg3myPlb.1225489089.1213610.tpo2@192.168.3.7>
Reformatted excerpts from Tomas Pospisek ML's message of 2008-10-31:
> When I start Sup, it starts eating my CPU and won't stop. And it
> doesn't seem to be doing anything either:
It could be indexing a large volume of mail. If you swap to the poll
buffer, you should be able to confirm that.
If you've just added some large mail sources, or something like that,
you might want to run sup-sync first to index them offline.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-10-31 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 21:38 Tomas Pospisek ML
2008-10-31 23:53 ` William Morgan [this message]
[not found] ` <6K5DuLg4.1225497709.2001540.tpo2@192.168.3.7>
2008-11-02 18:50 ` William Morgan
2008-11-03 20:45 ` Tomas Pospisek ML
2008-11-03 21:29 ` Tomas Pospisek ML
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=1225497126-sup-2054@entry \
--to=wmorgan-sup@masanjin.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