9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] upas problem
Date: Sat, 24 Jul 2010 15:17:42 -0400	[thread overview]
Message-ID: <802951dd2069dd90b350e155db89db95@kw.quanstro.net> (raw)
In-Reply-To: <AANLkTikV2wCNLD=6CDBGedHN06QuTi-hF9arQ+XBzyWs@mail.gmail.com>

> I have been accessing gmail from a standalone plan 9 terminal (pulled
> from sources and rebuilt kernel a few days ago) under vmware fusion
> 3.1.0. When I tried again recently:
>
> term% upas/fs -f /imaps/imap.gmail.com/my_email@gmail.com
>
> I enter my password and then
>
> a black square appears on the screen and "soverflow for fx->in" is
> printed repeatedly. This goes on for some time and then errors like:
>
> download 10423: short read 3084755 != 3571948: Hangup
>
> download 10424: i/o error: Hangup
>
> download 10425: i/o error: Hangup
>
> download 10426: i/o error: Hangup
>
> download 10427: i/o error: Hangup
>
> are printed in the window.
>
> I've seen this before, I previously had 4000 emails in my inbox and I
> got the these errors trying to open it. Now I have only 250 (2 or 3
> weeks worth) I have also only seen the "soverflow for fx->in" on
> vmware. On my native plan9 box I have only seen the hangup errors. I
> also seen the soverflow error when doing a pull (a big one) under
> vmware.

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.  i think incrementing a counter, rather than printing makes
more sense.  the version of pc/devether.c in 9atom does just that.

a bigger question is why you're getting queue overflows.
it could be that the virtualization is screwing with queue sizing.

nupas may also be helpful for big imap mailboxes;
unless viewed, email only gets downloaded once.

- erik



  reply	other threads:[~2010-07-24 19:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-24  9:59 James Chapman
2010-07-24 19:17 ` erik quanstrom [this message]
2010-07-24 19:44   ` Lyndon Nerenberg

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=802951dd2069dd90b350e155db89db95@kw.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).