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

diff --git a/contrib/systemd/haproxy.service.in b/contrib/systemd/haproxy.service.in
index 05fc595796c479b444a804119235388142decab9..bb77f0744cd5237a29677687456e008fd731d39d 100644 (file)
--- a/contrib/systemd/haproxy.service.in
+++ b/contrib/systemd/haproxy.service.in
@@ -1,6 +1,6 @@
 [Unit]
 Description=HAProxy Load Balancer
-After=network-online.target
+After=network-online.target rsyslog.service
 Wants=network-online.target
 
 [Service]