* Fwd: Increasing resolver timeout
[not found] <d61fa44c-05a9-aa88-aeb6-07735d582330@gmail.com>
@ 2019-11-08 17:20 ` Alberto Salvia Novella
0 siblings, 0 replies; only message in thread
From: Alberto Salvia Novella @ 2019-11-08 17:20 UTC (permalink / raw)
To: glibc developers
For example we have the following bug:
$ time ping -c1 "google.com""
0% packet loss
0m5,064s
$ time (ip=$(getent ahostsv4 "google.es" | awk '{ print $1 }' |
head -n1); ping -c1 "${ip}")
0% packet loss
0m0,042s
The extra time on the first case it's caused by a router mistakenly not
returning the IPv6 DNS reply, so the command just sits till it timeouts.
The point is this, the bug has been there for a long time unnoticed
simply because with 5s timeout the delay simply felt within normal. It
wasn't till I started programing server stuff where I noticed that
retrieving the data just took so long.
So probably we would be better having a longer timeout, like about 10s.
So if there is any network anomaly it would be obvious to any person
operating it.
Alberto <https://es20490446e.wordpress.com>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-11-08 17:20 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <d61fa44c-05a9-aa88-aeb6-07735d582330@gmail.com>
2019-11-08 17:20 ` Fwd: Increasing resolver timeout Alberto Salvia Novella
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).