From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] CPU at 99%
Date: Sun, 02 Nov 2008 10:50:36 -0800 [thread overview]
Message-ID: <1225651661-sup-1958@entry> (raw)
In-Reply-To: <6K5DuLg4.1225497709.2001540.tpo2@192.168.3.7>
Reformatted excerpts from Tomas Pospisek ML's message of 2008-10-31:
> The "[poll-mode]" buffer shows an "infinite amount" of the following
> message:
> [...]
> Found message at 44352220 with labels {Sent, unread}
> Found message at 44352220 with labels {Sent, unread}
> Found message at 44352220 with labels {Sent, unread}
> Found message at 44352220 with labels {Sent, unread}
> Found message at 44352220 with labels {Sent, unread}
What kind of source is this? I'm guessing mbox. Can you try to figure
out what is around byte offset 44352220 in that file? Sup isn't
advancing beyond that for some reason.
> When I do that I get an "eternal" (?) output of:
>
> [Sam Nov 01 01:00:53 +0100 2008] faking from for message
> sup-faked-b5d74cf19a1ebaf02e979448d059d0f4: Sup Auto-generated Fake
> Sender <sup at fake.sender.example.com>
> [Sam Nov 01 01:00:53 +0100 2008] faking date header for
> sup-faked-b5d74cf19a1ebaf02e979448d059d0f4
> [Sam Nov 01 01:00:53 +0100 2008] faking message-id for message from Sup
> Auto-generated Fake Sender <sup at fake.sender.example.com>:
> sup-faked-b5d74cf19a1ebaf02e979448d059d0f4
> [Sam Nov 01 01:00:53 +0100 2008] faking from for message
> sup-faked-b5d74cf19a1ebaf02e979448d059d0f4: Sup Auto-generated Fake
> Sender <sup at fake.sender.example.com>
> [Sam Nov 01 01:00:53 +0100 2008] faking date header for
> sup-faked-b5d74cf19a1ebaf02e979448d059d0f4
This is almost definitely the same problem as above.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-11-02 18:50 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
[not found] ` <6K5DuLg4.1225497709.2001540.tpo2@192.168.3.7>
2008-11-02 18:50 ` William Morgan [this message]
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=1225651661-sup-1958@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