Video conferencing software Users Info

2017-06-08 Thread Laura Franceschi
Hi, I'm writing to inform you that we have maintained a comprehensive mailing list of Video conferencing software Users across the Globe with emails, phone numbers and mailing addresses. We also have other technology users like: Mitel WebEx Nortel ShoreTel Avaya Juniper Networks

Re: Updates to the stable release process

2017-06-08 Thread Lukas Tribus
Hello! Am 08.06.2017 um 17:30 schrieb Willy Tarreau: > Hi all, > > William has joined Cyril an me in the stable maintenance team. We're now > three to have direct commit access, so don't be surprized if you see > new names in "git log --format=fuller" or in the gitweb interface. > That's a very

Re: exit error regression on haproxy1.8dev

2017-06-08 Thread Willy Tarreau
On Thu, Jun 08, 2017 at 08:37:28PM +0200, William Lallemand wrote: > On Thu, Jun 08, 2017 at 01:49:15PM +0200, William Lallemand wrote: > > > > You are right about the regression, however this part of the code should be > > called in daemon mode only, the regression was elsewhere :) > > > > Fix

Re: exit error regression on haproxy1.8dev

2017-06-08 Thread William Lallemand
On Thu, Jun 08, 2017 at 01:49:15PM +0200, William Lallemand wrote: > > You are right about the regression, however this part of the code should be > called in daemon mode only, the regression was elsewhere :) > > Fix attached. > Willy, could you apply this one? Thanks, -- William Lallemand

Re: [PATCH] BUG/MINOR: warning: 'need_resend' may be used uninitialized

2017-06-08 Thread Willy Tarreau
On Thu, Jun 08, 2017 at 07:30:39PM +0200, William Lallemand wrote: > The commit 201c07f68 ("MAJOR/REORG: dns: DNS resolution task and > requester queues") introduces a warning during compilation: > > src/dns.c: In function 'dns_resolve_recv': > src/dns.c:487:6: warning: 'need_resend' may be used

Re: [PATCH] BUG/MEDIUM: build without openssl broken

2017-06-08 Thread Willy Tarreau
On Thu, Jun 08, 2017 at 07:05:48PM +0200, William Lallemand wrote: > The commit 872f9c213 ("MEDIUM: ssl: add basic support for OpenSSL crypto > engine") broke the build without openssl support. Applied, thanks William. Willy

[PATCH] BUG/MINOR: warning: ‘need_resend’ may be used uninitialized

2017-06-08 Thread William Lallemand
The commit 201c07f68 ("MAJOR/REORG: dns: DNS resolution task and requester queues") introduces a warning during compilation: src/dns.c: In function ‘dns_resolve_recv’: src/dns.c:487:6: warning: ‘need_resend’ may be used uninitialized in this function [-Wmaybe-uninitialized] if (need_resend) {

[PATCH] BUG/MEDIUM: build without openssl broken

2017-06-08 Thread William Lallemand
The commit 872f9c213 ("MEDIUM: ssl: add basic support for OpenSSL crypto engine") broke the build without openssl support. The ssl_free_dh() function is not defined when USE_OPENSSL is not defined and leads to a compilation failure. --- src/haproxy.c | 2 +- 1 file changed, 1 insertion(+), 1

Updates to the stable release process

2017-06-08 Thread Willy Tarreau
Hi all, William has joined Cyril an me in the stable maintenance team. We're now three to have direct commit access, so don't be surprized if you see new names in "git log --format=fuller" or in the gitweb interface. In order to ease tracking of who handles what patch, we'll progressively start

RE: OneConnect feature in HAProxy

2017-06-08 Thread Gibson, Brian (IMS)
The IUS repos will have 1.7 I believe. https://ius.io/GettingStarted/ From: James Stroehmann [mailto:james.stroehm...@proquest.com] Sent: Thursday, June 08, 2017 10:27 AM To: Brendan Kearney ; haproxy@formilux.org Subject: RE: OneConnect feature in HAProxy Thanks for the info

RE: OneConnect feature in HAProxy

2017-06-08 Thread James Stroehmann
Thanks for the info - I will look into it but it looks like I'll have to upgrade to 1.6 first ... currently I'm using 1.5 out of the standard repositories for centos 7. Any pointers to a yum repo for 1.6 or 1.7? From: Brendan Kearney [mailto:bpk...@gmail.com] Sent: Thursday, May 25, 2017

RE: High Availability for haproxy itself

2017-06-08 Thread Gibson, Brian (IMS)
You could do something like this. Setup the haproxy status page on the haproxy server. Then create a bash script with syntax like this #!/bin/bash # value=$(curl -I http://www.example.org 2>/dev/null | head -n 1 | cut -d$' ' -f2) if [ $value -eq 200 ] then exit else exit 1 fi that will

Re: High Availability for haproxy itself

2017-06-08 Thread Markus Rietzler
Am 02.06.17 um 11:35 schrieb Raphaël Enrici: > Hi, > > if you are in a simple case where you only need some kind of active/passive > solution without big scaling needs on a > Linux system, look for "haproxy keepalived" on your favorite search engine, > you'll find many articles explaining the

HAPROXY HELP REQUIRED -- please contact

2017-06-08 Thread Vasudev Daxini
Regards, Vasudev Daxini,??RHCE (M) +91-9920347199

Re: exit error regression on haproxy1.8dev

2017-06-08 Thread William Lallemand
On Wed, Jun 07, 2017 at 02:13:58PM +0200, Emmanuel Hocdet wrote: > > > Le 7 juin 2017 à 10:34, Emmanuel Hocdet a écrit : > > > > Hi, > > > > ok: > >> haproxy -f test.cfg -W > >> echo $? > > 0 > > > > bad: > >> haproxy -f test.cfg > >> echo $? > > 1 > > > > With bunch of

subscribe

2017-06-08 Thread David Pollock
-- Any e-mail sent from Alternative Payments Ltd or its Group companies may contain information which is confidential and/or privileged. Unless you are the intended recipient you may not disclose, copy or use it; please notify the sender immediately and delete it and any copies. You should

RE: Regarding migration on version haproxy-1.7.3

2017-06-08 Thread Coscend@HAProxy
Hello Devendra, In the spirit of assisting, further to Pavlos' insights, you might want to check Baptiste Assman's blog on 1.5 vs. 1.6 below. It is our understanding that the new features in 1.6 have been mostly carried over to 1.7 as well.

Re: Regarding migration on version haproxy-1.7.3

2017-06-08 Thread Pavlos Parissis
On 06/08/2017 07:31 AM, Devendra Joshi wrote: > Hi, > currently we are using haproxy-1.5.14 & now we want to migrate on > haproxy-1.7.3 > > > is there any config changes or