From 4a95439a8dfd3f55be45c06e5e5994a6c6c2037f Mon Sep 17 00:00:00 2001
From: Markus Makela <markus.makela@mariadb.com>
Date: Fri, 9 Sep 2016 16:38:27 +0300
Subject: [PATCH] Don't restart even on abnormal failures

If systemd restarts MaxScale when an abnormal exit is detected, it is
likely to happen again. This leads into a loop which causes multiple
maxscale processes on the same machine. One example of this behavior is
when systemd times MaxScale out when it is starting.
---
 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 0ebeaeaab..982cbc00b 100644
--- a/etc/maxscale.service.in
+++ b/etc/maxscale.service.in
@@ -4,7 +4,7 @@ After=network.target
 
 [Service]
 Type=forking
-Restart=on-abnormal
+Restart=no
 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