From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Gnus refuses to connect after suspend and resume in different network, but Gnus in fresh emacs works
Date: Fri, 06 Jan 2023 15:22:40 +0100 [thread overview]
Message-ID: <87r0w7agjz.fsf@dod.no> (raw)
Platform: amd64, debian 11.6 "bullseye"
GNU Emacs 27.1,
Gnus v5.13 (native gnus of emas 27.1)
I started the emacs process at home and ran Gnus it in for several days.
Yesterday I unplugged gnus at home, and suspended the laptop.
Today I resumed the laptop in a different LAN and tried to plug in the
unplugged gnus.
But gnus was unable to connect.
So I stopped gnus and started gnus in the old emacs process, but gnus
was still unable to connect.
But gnus started from a fresh emacs process worked fine.
Is there a way to figure out what's gone wrong with the old emacs
process? I suspect a cached DNS server? Is there a way to find out if
that is the case?
Has anyone else observed this behaviour?
Does anyone know how to fix this (other than starting a new emacs)?
Thanks!
next reply other threads:[~2023-01-11 18:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 14:22 Steinar Bang [this message]
2023-01-12 8:50 ` Alberto Luaces
2023-01-12 21:42 ` Eric Abrahamsen
2023-01-13 7:55 ` Robert Pluim
2023-01-13 9:47 ` Alberto Luaces
2023-01-13 17:49 ` Eric Abrahamsen
2023-01-30 19:40 ` Steinar Bang
2023-01-30 20:48 ` Eric Abrahamsen
2023-01-30 19:31 ` Steinar Bang
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=87r0w7agjz.fsf@dod.no \
--to=sb@dod.no \
--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).