Re: [gnus git] branch master updated: n0-17-27-g43f8466 =1= nntp.el (nntp-open-connection): Set TCP keepalive option.

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> The use case is the one mentioned in the comment: you sit behind a NAT
> router.  Gnus connects, sends some commands, gets some responses, then
> sits still for some hours because the user goes on to do something else
> or reads newsgroup from another server (the machine may be put to sleep
> in the mean time, but not necessarily).  When the user comes back to
> this newsserver, the IP will often be the same as before, but the NAT
> router will have completely forgotten about this open TCP connection, so
> Emacs never receives an RST or anything like that and Gnus just sits
> there waiting for the answer that'll never come.

Right; makes sense.

But should this perhaps be a global Emacs thing?  Are there any
instances where switching TCP keepalive on is a bad thing?

I have a suspicion that just making Emacs 24 switch on TCP keepalive on
all connections (by default) would be a win.

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