[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170422223219.GJ17319@brightrain.aerifal.cx>
Date: Sat, 22 Apr 2017 18:32:19 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Re: [PATCH v2] attempts option not being respected in
resolv.conf
On Tue, Apr 04, 2017 at 02:08:08AM +0000, Stefan Sedich wrote:
> One thing I have found though is that the way the retry logic works if I
> want to retry ever 1 second for a total of 5 times I need to set it to
> 'options timeout:5 attempts:5', not sure if someone who knows this area
> well can comment but it appears to create a retry_interval based on
> timeout/attempts, which as far as I understand it is different to how it
> works with glibc where I can set timeout:1 attempts:5 and it does as I
> expect.
The man page documents timeout as "amount of time the resolver will
wait for a response from a remote name server before retrying the
query via a different name server". Since musl does not cycle through
servers, but tries them all concurrently, this definition does not
make sense, so we have to find a reasonable way to interpret the
options, but I agree it might be "wrong" right now. It might be that,
rather than retry_interval being timeout/attempts, retry_interval
should be timeout, and the total timeout should be timeout*attempts.
We really should look at the glibc behavior and see how it scales with
different settings and numbers of nameservers and try to make the
behavior somehow comparable.
BTW sorry I missed your V2.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
