From: Tassilo Horn <tassilo@member.fsf.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Oh Ma Gnus: (file-error "writing to process" "success" #<process *nnimap*<2>>)
Date: Tue, 14 Feb 2012 20:04:03 +0100 [thread overview]
Message-ID: <87r4xx6xuk.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <8739addz9n.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 14 Feb 2012 19:51:32 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
>> Do you have an idea why that error is only triggered at home but not
>> at work, and not at home when edebugging? I think, my network
>> connection at home is even a bit faster than here at work (32.000
>> KBit/s) which would somewhat support my timing hypothesis. But does
>> that make sense to you?
>
> Yes. The bug was in the handling of EAGAIN (i.e., a full write
> buffer) in the gnutls interface code. So if your network is slow
> you'd see the bug, but not otherwise.
What I've observed was the other way round: fast network => bang! slow
network (or code slowed down due to edebugging) => fine!
Anyway, great that it works again.
Bye,
Tassilo
next prev parent reply other threads:[~2012-02-14 19:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 19:10 Tassilo Horn
2012-02-13 19:29 ` Lars Ingebrigtsen
2012-02-13 19:40 ` Lars Ingebrigtsen
2012-02-13 19:53 ` Tassilo Horn
2012-02-13 20:13 ` Tassilo Horn
2012-02-13 20:28 ` Lars Ingebrigtsen
2012-02-13 20:51 ` Lars Ingebrigtsen
2012-02-14 7:29 ` Tassilo Horn
2012-02-14 18:35 ` Tassilo Horn
2012-02-14 18:51 ` Lars Ingebrigtsen
2012-02-14 18:51 ` Lars Ingebrigtsen
2012-02-14 19:04 ` Tassilo Horn [this message]
2012-02-13 21:10 ` Tassilo Horn
2012-02-13 19:50 ` Tassilo Horn
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=87r4xx6xuk.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--cc=ding@gnus.org \
--cc=larsi@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).