From: Apollon Oikonomopoulos <apoikos@debian.org>
Date: Sun, 25 Mar 2018 09:31:50 +0000 (+0200)
Subject: Start after rsyslog.service
X-Git-Tag: archive/raspbian/2.6.7-1+rpi1^2~4
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=01b30ab5347de306ecb5be3fe54e514b5cbf3cdf;p=haproxy.git

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 eb1ad42..7361107 100644
--- 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]