From 4b7cec504ad239d375f4f3e84fc375b0ccf7c63c Mon Sep 17 00:00:00 2001
From: Markus Makela <markus.makela@mariadb.com>
Date: Thu, 17 Dec 2015 10:23:47 +0200
Subject: [PATCH] Changed maxscale.service restart values

The maxscale service will be restarted only if the process is down because
a signal was caught or the process times out. If the process would be restarted
when it exits with a non-zero value, this would lead to infinite loops when
there is a configuration error.
---
 etc/maxscale.service.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/etc/maxscale.service.in b/etc/maxscale.service.in
index f21de6e7b..0df1c7aba 100644
--- a/etc/maxscale.service.in
+++ b/etc/maxscale.service.in
@@ -4,7 +4,7 @@ After=network.target
 
 [Service]
 Type=forking
-Restart=on-failure
+Restart=on-abnormal
 PIDFile=@MAXSCALE_VARDIR@/run/maxscale/maxscale.pid
 ExecStartPre=/usr/bin/install -d @MAXSCALE_VARDIR@/run/maxscale -o maxscale -g maxscale
 ExecStart=@CMAKE_INSTALL_PREFIX@/@MAXSCALE_BINDIR@/maxscale --user=maxscale