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 49d3c52cf1c1d2e83ca6fc6c9eb4fc9f7138aca5..b93545585037c8fbde245f26fb6dc14bb5307bb7 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]