Re: new wifi connection = nntp timeout = Emacs restart?

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Robert Pluim <rpluim@gmail.com> writes:
>
>>>>>>> On Sun, 19 Apr 2020 10:32:03 -0700, Eric Abrahamsen
>> <eric@ericabrahamsen.net> said:
>>     Eric> Yeah, I used to assume I was hallucinating, but it's been going on for
>>     Eric> too long now. The rest of what you describe below is perfectly "normal"
>>     Eric> for Gnus, and the same as what we all experience, but this restarting
>>     Eric> thing... Next time I switch networks (not all that often, these days)
>>     Eric> I'll do some edebugging and try to open a more detailed bug report.
>>
>> I see this too. Every time I try to look at it, itʼs an issue
>> somewhere deep in Emacs' networking code where itʼs trying to read
>> from the network and failing, but not failing enough that it gets an
>> error or a timeout. And then Real Life™ intervenes and I *have* to get
>> Gnus working again.
>>
>> Iʼve tried turning on tcp-keepalives, but that doesnʼt help either.
>
> I just started watching Emacs' nntp connections, and immediately noticed
> that closing all servers ("z") and re-opening them ("g") does not kill
> the previous connection, it just opens a new one, with it's own
> keepalive timer.
>
> If I kill Gnus, it kills all the open connections, but maybe there's
> something about switching networks that prevents it from killing the
> connections? And then we try to use a stale connection? I will test
> more.
>
> But doesn't it seem basically wrong that `gnus-close-server' on an nntp
> server doesn't kill the network connection?

It's "z" suspending Gnus that doesn't work, "C" on the nntp server in
the *Server* buffer kills the connection correctly. Using "z" apparently
does not set the `nntp-server-buffer' correctly -- the
"(nntp-find-connection nntp-server-buffer)" call returns nil.

One step at a time...