summaryrefslogtreecommitdiff
path: root/sys/src/cmd/python/Python/atof.c
diff options
context:
space:
mode:
authorsl <sl@stanleylieber.com>2021-02-19 21:29:55 -0500
committersl <sl@stanleylieber.com>2021-02-19 21:29:55 -0500
commit4bbb3b0b21edd81be37a0a6ad12c76a63d127bed (patch)
treef57ff08220429c84e201e201df8106a44aaf3ec2 /sys/src/cmd/python/Python/atof.c
parent29e8ea26f2f9af2b9924e16dffd784bc5ae5685e (diff)
/sys/src/cmd/ndb/dns.h:
--- To: 9front@9front.org Date: Sun, 07 Feb 2021 14:56:39 +0100 From: kvik@a-b.xyz Subject: Re: [9front] transient dns errors cause smtp failure Reply-To: 9front@9front.org I think I found a reason for DNS failing on known good domains. /sys/src/cmd/ndb/dns.h:156,157 /* tune; was 60*1000; keep it short */ Maxreqtm= 8*1000, /* max. ms to process a request */ So, 8 seconds is how much the resolver will bother with a request it has been handed, before dropping it on the floor with little explanation. It seems quite possible that this is too short a timeout on a machine during a spam queue run, which predictably stresses the compute and network resources. In turn, negative response caching might explain why a particular unlucky domain would basically stop receiveing any mail for a while. I'm dying to know if bumping this limit would clear up the queue of such DNS errors. --- [narrator: it did.]
Diffstat (limited to 'sys/src/cmd/python/Python/atof.c')
0 files changed, 0 insertions, 0 deletions