From: James Chapman <james@cs.ioc.ee>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] soverflow for fx->in
Date: Sun, 25 Jul 2010 03:33:45 +0300 [thread overview]
Message-ID: <AANLkTikHogzkNszF8aiU=jK1ijVwEv-Y9uk=Oh0nf5m1@mail.gmail.com> (raw)
On Sat, Jul 24, 2010 at 10:44 PM, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
>> what's happening is that the printing of "soverflow for fx->in"
>> is wasting so much time that the imap server gets bored and hangs
>> up.
>
> This is really dragging out for 30 minutes?
No. Not that long.
Also, I just did a pull from sources which appears to have updated
almost the complete contents of /386. This caused the "soverflow for
fx->in" message to appear. I had to run pull three times to get it to
finish.
James
next reply other threads:[~2010-07-25 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 0:33 James Chapman [this message]
2010-07-25 4:52 ` erik quanstrom
2010-07-25 9:57 ` James Chapman
[not found] <<4B4622FF-CD80-4466-9D07-316E2835D10F@pvv.ntnu.no>
2009-10-26 20:53 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2009-10-26 16:33 Andreas Eriksen
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='AANLkTikHogzkNszF8aiU=jK1ijVwEv-Y9uk=Oh0nf5m1@mail.gmail.com' \
--to=james@cs.ioc.ee \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).