Refactor how we restart FS when neccesary

Sometimes RCCN updates require FS to restart, we don't do this because
we don't want to drop calls, instead we were waiting till the nighttime
when it's likely there are no calls, (we still didn't drop them)

Let's issue a shutdown elegant right away, so FS will restart as soon as 'possible'

modules/rhizo_base/files/bin/notify-freeswitch.sh

@@ -0,0 +1,17 @@
+#!/bin/bash
+
+# Puppet has made some change that requires a Freeswitch restart.
+# Place flag file anyway as fallback. Service will delete it
+if [ ! -f /tmp/FS-dirty ] ; then
+  echo 1 > /tmp/FS-dirty
+fi
+
+if [ `/usr/bin/fs_cli -x 'fsctl shutdown_check'` == "true" ] ; then
+  exit
+fi
+
+# Trigger an "elegant" shutdown -
+# (Shutdown when there are no active calls, but don't disable service in the meantime)
+# This won't return until FS actually shuts down.
+exec /usr/bin/fs_cli -x 'fsctl shutdown elegant' &
+

modules/rhizo_base/files/freeswitch.service

@@ -8,6 +8,7 @@ PIDFile=/run/freeswitch/freeswitch.pid
 Environment="DAEMON_OPTS=-nonat"
 EnvironmentFile=-/etc/default/freeswitch
 ExecStart=/usr/bin/freeswitch -u root -g freeswitch -ncwait $DAEMON_OPTS
+ExecStopPost=/bin/sh -c "if [ -f /tmp/FS-dirty ]; then rm /tmp/FS-dirty; fi"
 TimeoutSec=45s
 Restart=always
 User=root