Sponsored contribution for haproxy.org
Hi there,
My name is Rick Manarauskis. I create & curate new content at PiketMedia.
I was looking for relevant people to potentially work with and haproxy.org
popped up on my radar, which is why I'm reaching out to you.
I would love to send you a couple of
Hi,
A couple of patches for the DNS runtime resolver:
#1 is just a typo cleanup
#2 fixes a "regression" introduced with the parsing of the Additional
section from the SRV record responses. Basically, when HAProxy uses SRV
records and Additional sections together, a server may not recover from its
I've modified build system again.
please consider that as a final effort from me. If you are not happy enough
with it, you are free to improve it.
пт, 31 июл. 2020 г. в 14:24, Илья Шипицин :
>
>
> пт, 31 июл. 2020 г. в 14:14, Willy Tarreau :
>
>> On Fri, Jul 31, 2020 at 01:01:49PM +0500, ???
Hello,
for example, I'm running tcp balancing with several backend.
is it possible to mark first backend for "established" connections ?
i.e. all connections that established, still go to marked backend. no new
connection are established (once I see there are no more connections, I can
turn it of
Hi All,
Not sure if i hit a bug or a config problem, so before creating a bug report
i'll ask the maillinglist.
i'm running a small haproxy setup, nothing fancy yet, it's just designed so the
client can upgrade to a multi cluster setup in no time.
Running debian stretch with 1.8.25-1~bpo9+1, t
Hi,
On Tue, 2020-08-04 at 16:54 +0500, Илья Шипицин wrote:
> for example, I'm running tcp balancing with several backend.
> is it possible to mark first backend for "established" connections ?
You want to set whole backend (and not just one server) to drain(established
only) ?
> i.e. all connect
Yeah, I mean server of course. Thank for the link
On Tue, Aug 4, 2020, 5:28 PM Jarno Huuskonen wrote:
> Hi,
>
> On Tue, 2020-08-04 at 16:54 +0500, Илья Шипицин wrote:
> > for example, I'm running tcp balancing with several backend.
> > is it possible to mark first backend for "established" conne
❦ 4 août 2020 14:10 +02, Bram Gillemon:
> Running debian stretch with 1.8.25-1~bpo9+1, this morning the package
> upgraded to 1.8.26-1~bpo9+1 and i started noticing some strange
> behaviour.
For reference:
HA-Proxy version 1.8.26-1~bpo9+1 2020/08/03
Copyright 2000-2020 Willy Tarreau
Build op
Hello,
I've seen the package is available now. Thank you.
Le 03/08/2020 à 22:49, Vincent Bernat a écrit :
>
> Well, you are the second person asking this in a short time, so I will
> provide one. My rationale is that 2.2 is quite new and Stretch is
> already maintained as LTS. When maintained as
Willy,
It appears that the SUBVERS file is broken for 2.2 snapshots:
> [timwolla@/tmp]curl -fsSL
> 'http://www.haproxy.org/download/2.2/src/snapshot/haproxy-ss-LATEST.tar.gz'
> |tar -O -xvz --wildcards '*/SUBVERS'
> haproxy-ss-20200801/SUBVERS
> -$Format:%h$
It looks good for 2.1:
> [timwolla
Hi Tim,
On Tue, Aug 04, 2020 at 06:14:41PM +0200, Tim Düsterhus wrote:
> Willy,
>
> It appears that the SUBVERS file is broken for 2.2 snapshots:
>
> > [timwolla@/tmp]curl -fsSL
> > 'http://www.haproxy.org/download/2.2/src/snapshot/haproxy-ss-LATEST.tar.gz'
> > |tar -O -xvz --wildcards '*/SUBV
Willy,
Am 04.08.20 um 18:34 schrieb Willy Tarreau:
> That's rather strange. I'm still comparing the two repos, they look
> exactly similar.
>
> Ah found it! We don't just need the "atttributes" file but also the
> info/attributes one. I don't remember which one is used when. I'm
> going to update
On Tue, Aug 04, 2020 at 06:49:40PM +0200, Tim Düsterhus wrote:
> Willy,
>
> Am 04.08.20 um 18:34 schrieb Willy Tarreau:
> > That's rather strange. I'm still comparing the two repos, they look
> > exactly similar.
> >
> > Ah found it! We don't just need the "atttributes" file but also the
> > info
On Tue, Aug 04, 2020 at 03:55:04PM +0500, ??? wrote:
> I've modified build system again.
> please consider that as a final effort from me. If you are not happy enough
> with it, you are free to improve it.
Thanks Ilya. I think that will be OK this way. I'll add commit
messages and will ta
Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses t
15 matches
Mail list logo
