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/admin/systemd/haproxy.service.in b/admin/systemd/haproxy.service.in
index eb1ad428b9185dcaa9070cbc116bc5477d4a234f..7361107d8a3896be4eefb571d378d6d750c7826f 100644 (file)
--- a/admin/systemd/haproxy.service.in
+++ b/admin/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]