From 34029b0ef8265bec84930bfd1146b53c98555655 Mon Sep 17 00:00:00 2001 From: Apollon Oikonomopoulos Date: Sun, 25 Mar 2018 11:31:50 +0200 Subject: [PATCH] Start after rsyslog.service As HAProxy is running chrooted by default, we rely on an additional syslog socket created by rsyslog inside the chroot for logging. As this socket cannot trigger syslog activation, we explicitly order HAProxy after rsyslog.service. Note that we are not using syslog.service here, since the additional socket is rsyslog-specific. Forwarded: no Last-Update: 2017-12-01 Gbp-Pq: Name haproxy.service-start-after-syslog.patch --- contrib/systemd/haproxy.service.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/systemd/haproxy.service.in b/contrib/systemd/haproxy.service.in index 74e66e3..243acf2 100644 --- a/contrib/systemd/haproxy.service.in +++ b/contrib/systemd/haproxy.service.in @@ -1,6 +1,6 @@ [Unit] Description=HAProxy Load Balancer -After=network.target +After=network.target rsyslog.service [Service] Environment="CONFIG=/etc/haproxy/haproxy.cfg" "PIDFILE=/run/haproxy.pid" -- 2.30.2