From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: [gnus git] branch master updated: n0-17-27-g43f8466 =1= nntp.el (nntp-open-connection): Set TCP keepalive option.
Date: Tue, 10 May 2011 15:07:19 +0200 [thread overview]
Message-ID: <uay62en1q0.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87y62epwwg.fsf@gmail.com>
Antoine Levitt <antoine.levitt@gmail.com> writes:
> 10/05/11 14:06, Greg Troxel
>>> (And, besides, if nntp.el needs keepalive, doesn't all network
>>> connections need it?)
>>
>> That is a fair point.
>>
>> Another approach would be to have gnus have a timer so that it tears
>> down news connections after some period of inactivity, like perhaps
>> 600s. It seems that perhaps a gnus left idle for hours shouldn't have
>> any open connections.
>
> I have no idea if that's relevant to the discussion at hand, but in my
> use case there is: I suspend my computer on the evening, and switch it
> back on in the morning, creating large periods of idle for gnus. Since
> connections are to localhost, either by NNTP with leafnode or by IMAP
> with dovecot, I don't think any are lost.
>
> I've seen nnimap bug out on this use case (mainly not getting new mail),
> although I think nntp is fine.
>
just FYI, I frequently have to kill gnus and then wait for a period of
time before a nntp session can be reconnected to eternalseptember nntp
servers. Invariably it hangs on post but I haven't noticed a reliable
"case" with which to duplicate the issue. It happens frequently however.
prev parent reply other threads:[~2011-05-10 13:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1QJYrH-0001ys-1x@quimby.gnus.org>
2011-05-09 22:53 ` Lars Magne Ingebrigtsen
2011-05-10 1:01 ` Stefan Monnier
2011-05-10 1:07 ` Stefan Monnier
2011-05-30 20:14 ` Lars Magne Ingebrigtsen
2011-05-30 20:17 ` Lars Magne Ingebrigtsen
2011-05-10 5:30 ` David Engster
2011-05-10 13:46 ` Stefan Monnier
2011-05-10 14:19 ` David Engster
2011-05-11 8:57 ` David Engster
2011-05-11 17:59 ` David Engster
2011-05-10 12:06 ` Greg Troxel
2011-05-10 12:23 ` Antoine Levitt
2011-05-10 13:07 ` Richard Riley [this message]
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=uay62en1q0.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--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).