the exit 0 at the end of the script means we will always exit with 0
which means the return 1 statements are useless.
let start_scheduler() return the correct value depending on result.
currently, it will return 1 in line 80
echo "Service batch isn't running but stale lock file exists"
echo "Removing stale lock file at $LOCKFILE"
rm -f $LOCKFILE
start_scheduler
return 1

Regardless of the actual result.
bounce KDP3 to latest ver.
bounce to latest KDP3 ver.
while the returncode is what determines the monitor's result, it is also
customary to reflect the status in the output.
good for say, getting it by mail, or when running from CLI or when you
are color blind looking at the Nagios I/F :)
reported by Martin Schygulla from SAP.
never use short tags.
never use short tags
Merge branch 'master' of https://github.com/jessp01/server
never use short tags

reported by Martin Schygulla from SAP.
never use short tags.
Merge branch 'master' of https://github.com/jessp01/server
wrong paths to logs.
Merge branch 'master' of https://github.com/jessp01/server
reverting changes and will open a pull per fix in separate branches.
sigh
the exit 0 at the end of the script means we will always exit with 0
let start_scheduler() return the correct value depending on result.
currently, it will return 1 in line 80
echo "Service batch isn't running but stale lock file exists"
echo "Removing stale lock file at $LOCKFILE"
rm -f $LOCKFILE
start_scheduler
return 1
.
Merge pull request #1207 from jessp01/batch-init-fix

Batch init fix