[PATCH] Resolv: re-read SRV query every time if its TTL is 0

[Jakub Hrozek]

This is a follow-up to my previous patches that read the TTL values from
SRV queries. Apparently, the failover code explicitly guarded against
timeout=0. I don't think it makes much sense, either the timeout is read
from DNS in which case we should retry always or it's a negative timeout
which should have the same semantics (and sholdn't be zero anyway).

[Pavel Březina]

On 03/24/2015 12:05 PM, Jakub Hrozek wrote:
>  This is a follow-up to my previous patches that read the TTL values
> from
>  SRV queries. Apparently, the failover code explicitly guarded against
>  timeout=0. I don't think it makes much sense, either the timeout is read
>  from DNS in which case we should retry always or it's a negative timeout
>  which should have the same semantics (and sholdn't be zero anyway). 
Ack.

[Jakub Hrozek]

On Tue, Mar 24, 2015 at 12:23:36PM +0100, Pavel Březina wrote:
>  On 03/24/2015 12:05 PM, Jakub Hrozek wrote:
>  >This is a follow-up to my previous patches that read the TTL values from
>  >SRV queries. Apparently, the failover code explicitly guarded against
>  >timeout=0. I don't think it makes much sense, either the timeout is read
>  >from DNS in which case we should retry always or it's a negative timeout
>  >which should have the same semantics (and sholdn't be zero anyway).
>  
>  Ack. 
CI: http://sssd-ci.duckdns.org/logs/job/11/53/summary.html
* master: 9797aa5907191cef5db8279e20ec75fd0abbe980
* sssd-1-12: 9dd8510d5d95d8ff7170f29ef4d9c603b3573cfe