Re: Fix triggering of runtime DNS resolution?

Hi Conrad, Please use the two patches in attachement. Baptiste From c19188e50313616833f0a6b3d5b1373c8f5bac78 Mon Sep 17 00:00:00 2001 From: Baptiste Assmann Date: Thu, 3 Sep 2015 10:59:39 +0200 Subject: [PATCH 02/10] MINOR: BUGFIX: DNS resolution doesn't start Patch

Re: Fix triggering of runtime DNS resolution?

Hi Baptiste (and others), I can confirm that the two patches applied make this work as expected for me (first resolution at first health check, then not again until hold.valid is elapsed). Thanks a lot! I am still wondering if the signature of tick_* shouldn't also be changed to unsigned int? I

Re: Fix triggering of runtime DNS resolution?

On Thu, Sep 3, 2015 at 1:11 AM, Baptiste wrote: > On Thu, Sep 3, 2015 at 12:56 AM, Conrad Hoffmann > wrote: >> Hello, >> >> it's kind of late and I am not 100% sure I'm getting this right, so would >> be great if someone could double-check this: >> >>

Re: Fix triggering of runtime DNS resolution?

On Thu, Sep 3, 2015 at 12:56 AM, Conrad Hoffmann wrote: > Hello, > > it's kind of late and I am not 100% sure I'm getting this right, so would > be great if someone could double-check this: > > Essentially, the runtime DNS resolution was never triggered for me. I > tracked

Fix triggering of runtime DNS resolution?

Hello, it's kind of late and I am not 100% sure I'm getting this right, so would be great if someone could double-check this: Essentially, the runtime DNS resolution was never triggered for me. I tracked this down to a signed/unsigned problem in the usage of tick_is_expired() from checks.c:2158.