From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47431@debbugs.gnu.org, hongyi.zhao@gmail.com
Subject: bug#47431: Process Whois connection broken by remote peer.
Date: Sun, 28 Mar 2021 16:19:34 +0200 [thread overview]
Message-ID: <87wntrqs21.fsf@gnus.org> (raw)
In-Reply-To: <83wntrmkja.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 28 Mar 2021 17:15:37 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I think we should simply update the list of servers we use, it sounds
> like what we have is outdated. The default should be useful and
> easily reachable. But I'm not an expert on this stuff.
Oh, sure; we should fix whois.el. I was just wondering whether there
was something odd going on in our basic networking layer here.
I let the connect run for longer, and I do seem to reliably get timeouts
here. It's just that they take a long time -- this one ran for about
five minutes before I got:
Debugger entered--Lisp error: (file-error "Failed connect" "Connection timed out")
make-network-process(:name "Whois" :buffer #<buffer *scratch*> :host "rs.internic.net" :service 43 :nowait nil :tls-parameters nil :coding nil)
That is an excessive timeout... but I guess this is up to the OS? We
don't specify a timeout in the make-network-process function, I think?
(It's been a while since I've read it...)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-03-28 14:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 1:39 bug#47431: Process Whois connection broken by remote peer Hongyi Zhao
2021-03-27 6:30 ` Eli Zaretskii
2021-03-27 7:23 ` Gregory Heytings
2021-03-27 8:08 ` Eli Zaretskii
2021-03-27 11:01 ` Gregory Heytings
2021-03-27 11:04 ` Gregory Heytings
2021-03-28 15:39 ` Lars Ingebrigtsen
2021-03-28 20:23 ` Gregory Heytings
2021-03-29 0:19 ` Hongyi Zhao
2021-03-29 4:50 ` Eli Zaretskii
2021-03-29 7:35 ` Gregory Heytings
2021-03-29 8:38 ` Eli Zaretskii
2021-03-29 11:31 ` Gregory Heytings
2021-03-29 12:02 ` Eli Zaretskii
2021-03-29 12:12 ` Gregory Heytings
2021-03-29 14:16 ` Hongyi Zhao
2021-03-29 10:58 ` Lars Ingebrigtsen
2021-03-29 11:20 ` Gregory Heytings
2021-03-29 12:19 ` Gregory Heytings
2021-03-30 13:22 ` Lars Ingebrigtsen
2021-03-31 7:53 ` Gregory Heytings
2021-03-31 13:39 ` Lars Ingebrigtsen
2021-03-31 14:27 ` Gregory Heytings
2021-04-14 14:55 ` Stefan Kangas
2022-06-28 13:40 ` Lars Ingebrigtsen
2022-07-28 10:35 ` Lars Ingebrigtsen
2022-07-28 21:56 ` Gregory Heytings
2022-07-29 11:34 ` Lars Ingebrigtsen
2021-03-27 9:50 ` Hongyi Zhao
2021-03-27 9:57 ` Hongyi Zhao
2021-03-27 10:33 ` Eli Zaretskii
2021-03-27 12:29 ` Hongyi Zhao
2021-03-27 13:44 ` Eli Zaretskii
2021-03-28 1:41 ` Hongyi Zhao
2021-03-28 6:38 ` Eli Zaretskii
2021-03-28 7:12 ` Hongyi Zhao
2021-03-28 14:11 ` Lars Ingebrigtsen
2021-03-28 14:15 ` Eli Zaretskii
2021-03-28 14:19 ` Lars Ingebrigtsen [this message]
2021-03-28 14:55 ` Lars 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wntrqs21.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47431@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=hongyi.zhao@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).