On Fri, Feb 08, 2013 at 11:27:31PM +0400, Samat Galimov wrote:
> You are right.
> After I start haproxy with patch it establishes first connection normally,
> as it should.
> All following connections are randomly dropping an error as before.
OK, so maybe there are still some places where the chan
You are right.
After I start haproxy with patch it establishes first connection normally,
as it should.
All following connections are randomly dropping an error as before.
On Thu, Feb 7, 2013 at 11:09 PM, Willy Tarreau wrote:
> On Thu, Feb 07, 2013 at 09:22:37PM +0400, Samat Galimov wrote:
> >
Signed-off-by: Marc-Antoine Perennou
---
.gitignore | 1 +
Makefile | 8 ++--
contrib/systemd/haproxy.service.in | 11 +++
3 files changed, 18 insertions(+), 2 deletions(-)
create mode 100644 contrib/systemd/haproxy.service.in
diff
Signed-off-by: Marc-Antoine Perennou
---
doc/haproxy-en.txt | 1 +
doc/haproxy-fr.txt | 1 +
doc/haproxy.1 | 4
include/types/global.h | 1 +
src/haproxy.c | 35 +++
5 files changed, 30 insertions(+), 12 deletions(-)
diff --git a
Hi,
Currently, to reload haproxy configuration, you have to use "-sf".
Systemd philosophy is for the daemon not to fork by themselves, but rather let
the init process do it for them.
My first patch adds a new option "-Ds" which is exactly like "-D", but instead
of
forking n times to get n jobs
Signed-off-by: Marc-Antoine Perennou
---
.gitignore| 1 +
Makefile | 16 +-
src/haproxy-systemd-wrapper.c | 122 ++
3 files changed, 137 insertions(+), 2 deletions(-)
create mode 100644 src/haproxy-systemd-wr
6 matches
Mail list logo