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 9b7c3d1bbcad7811609bf23c887ca38a066aa3ba..91d226868cd88d2e1960acf5b6f5743cd1a532c6 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.target
+After=network.target rsyslog.service
 
 [Service]
 EnvironmentFile=-/etc/default/haproxy