Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: nnimap gets confused after hardware suspend/resume
Date: Tue, 12 Apr 2011 17:48:20 +0200	[thread overview]
Message-ID: <m362qjo4hn.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87y63iug4c.fsf@gmail.com>

Antoine Levitt <antoine.levitt@gmail.com> writes:

> I'm not sure where to look to debug this further, but I'd be happy to
> provide more information if needed.

I'm not sure how to debug this, either.

I've tried to reproduce various kinds of network failures, mostly by
switching off gnutls support, and killing the external gnutls-cli
program.  But whatever I do, Gnus just reconnects.

Does anybody have a convenient way to reproduce convincing network
failures?

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/




  parent reply	other threads:[~2011-04-12 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10 18:16 Antoine Levitt
2011-04-10 20:21 ` Tassilo Horn
2011-04-12 15:48 ` Lars Magne Ingebrigtsen [this message]
2011-04-12 17:35   ` Antoine Levitt
2011-04-12 17:44     ` Lars Magne Ingebrigtsen

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=m362qjo4hn.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@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).