Le 13/05/2017 à 08:09, Willy Tarreau a écrit :
> Hi Benoît,
>
> On Sat, May 13, 2017 at 07:32:10AM +0200, Benoît GARNIER wrote:
>> Le 12/05/2017 à 15:54, Willy Tarreau a écrit :
>>> Hi Benoît,
>>>
>>> On Thu, May 04, 2017 at 08:50:33AM +0200, Benoît GARNIER wrote:
>>> (...)
If you do the
Hi Benoît,
On Sat, May 13, 2017 at 07:32:10AM +0200, Benoît GARNIER wrote:
> Le 12/05/2017 à 15:54, Willy Tarreau a écrit :
> > Hi Benoît,
> >
> > On Thu, May 04, 2017 at 08:50:33AM +0200, Benoît GARNIER wrote:
> > (...)
> >> If you do the following operation : time_t => localtime() => struct tm
On Sat, May 13, 2017 at 08:44:06AM +0200, Benoît GARNIER wrote:
> Time handling is not easy. I hate to say that, but POSIX and glibc
> manage to make it even harder. Especially the timezone global handling
> which is not thread-safe as you pinpointed.
> Anyway, free conding a simple timegm() is
Le 13/05/2017 à 09:46, Willy Tarreau a écrit :
> On Sat, May 13, 2017 at 08:44:06AM +0200, Benoît GARNIER wrote:
>> Time handling is not easy. I hate to say that, but POSIX and glibc
>> manage to make it even harder. Especially the timezone global handling
>> which is not thread-safe as you
On Sat, May 13, 2017 at 10:42:58AM +0200, Benoît GARNIER wrote:
> Le 13/05/2017 à 09:46, Willy Tarreau a écrit :
> > On Sat, May 13, 2017 at 08:44:06AM +0200, Benoît GARNIER wrote:
> >> Time handling is not easy. I hate to say that, but POSIX and glibc
> >> manage to make it even harder.
Le 13/05/2017 à 11:27, Willy Tarreau a écrit :
> On Sat, May 13, 2017 at 10:42:58AM +0200, Benoît GARNIER wrote:
>> Le 13/05/2017 à 09:46, Willy Tarreau a écrit :
>>> On Sat, May 13, 2017 at 08:44:06AM +0200, Benoît GARNIER wrote:
Time handling is not easy. I hate to say that, but POSIX and
Hi all,
The version of haproxy I use is:
# haproxy -version
HA-Proxy version 1.5.2 2014/07/12
Copyright 2000-2014 Willy Tarreau
I have a question regarding the Health Check. In the documentation of
haproxy, it mentions the below for the "timeout check" and "inter":
For
Hi all,
As Willy said, I'm reviewing the internal DNS architecture to make it fully
autonomous and more flexible with a registration mechanism and callbacks
system.
First purpose is to mutualise DNS resources (cache of the response, one
resolution at a time for a query), second is to enable dns
8 matches
Mail list logo