Wow. Really appreciate you following up. Thanks Willy!
Patrick Overbey
Fiserv
-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu]
Sent: Friday, March 29, 2019 4:01 PM
To: maio...@gmail.com; Overbey, Patrick (Sioux Falls)
Cc: haproxy@formilux.org
Subject: Upcoming haproxy build
Hi,
I finally could figure how to work around the issues with very old
linkers. I could work on this using a very old AIX machine we have
here running AIX 5.1, so now that my test code works on it, I'm
fairly confident more recent versions will as well, and given that
Jeffrey's errors on Cygwin
Am 29.03.2019 um 14:25 schrieb Willy Tarreau:
> Hi Aleks,
>
> On Fri, Mar 29, 2019 at 02:09:28PM +0100, Aleksandar Lazic wrote:
>> With openssl are 2 tests failed but I'm not sure because of the setup or a
>> bug.
>> https://gitlab.com/aleks001/haproxy19-centos/-/jobs/186769272
>
> Thank you
Hi Aleks,
On Fri, Mar 29, 2019 at 02:09:28PM +0100, Aleksandar Lazic wrote:
> With openssl are 2 tests failed but I'm not sure because of the setup or a
> bug.
> https://gitlab.com/aleks001/haproxy19-centos/-/jobs/186769272
Thank you for the quick feedback. I remember about the first one being
Am 29.03.2019 um 11:50 schrieb Willy Tarreau:
> Hi,
>
> HAProxy 1.9.6 was released on 2019/03/29. It added 34 new commits
> after version 1.9.5.
>
> As mentioned in the 2.0-dev2 release, we've addressed quite a number
> of issues recently and these fixes have now been backported into this
>
Hi,
HAProxy 1.9.6 was released on 2019/03/29. It added 34 new commits
after version 1.9.5.
As mentioned in the 2.0-dev2 release, we've addressed quite a number
of issues recently and these fixes have now been backported into this
release.
Two issues affect checks and may occasionally cause
N¬Æ§Kó0K"wë,j»÷Pý:]xÐAãPÓNûm¸ S¡h¥$Ú®·»
pµë
©®r~æ[±¢¸!jèÇ'è®h¥»++ç-n4Ñ ¨ ±ºh²ÐÚµákoLj½´×ÝtãÝ·ûM4Ð*'µéí-©à¹¨ uàÄ
íz{SÊ{¦V¢ÈZ®Ç
Hi Ricardo,
On Thu, Mar 28, 2019 at 10:15:41PM -0300, Ricardo Nabinger Sanchez wrote:
> Hello,
>
> We have been chasing a segfault for a few weeks and today we were able
> to track it down. There is a null-pointer dereferencing when using
> tcp-check connect; although we don't know yet as to
Hi.
Am 29.03.2019 um 09:34 schrieb Matous Jan Fialka:
> Hello,
>
> please consider adding range iterator item variable (say `rng.iteritem`) for
> the `server-template` directive so that it can be expanded in the
> `:`
> part of the statement or anywhere else where applicable (see in the example
Hello,
please consider adding range iterator item variable (say
`rng.iteritem`) for
the `server-template` directive so that it can be expanded in the
`:`
part of the statement or anywhere else where applicable (see in the
example snippet
below).
Also to have general zero-padding converter
10 matches
Mail list logo
