From ca1f70b8859aae36ad66aee3716f20647b822772 Mon Sep 17 00:00:00 2001
From: Sebastian Grewe <sebastian@grewe.ca>
Date: Fri, 7 Feb 2014 13:01:28 +0100
Subject: [PATCH] [UPDATE] Use proper endCronjob in PPS RPC checks

---
 cronjobs/pps_payout.php | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/cronjobs/pps_payout.php b/cronjobs/pps_payout.php
index 06cb843e..fc91645f 100755
--- a/cronjobs/pps_payout.php
+++ b/cronjobs/pps_payout.php
@@ -39,11 +39,8 @@ if ( $bitcoin->can_connect() === true ){
   if (is_array($dDifficulty) && array_key_exists('proof-of-work', $dDifficulty))
     $dDifficulty = $dDifficulty['proof-of-work'];
 } else {
-  $log->logFatal("Aborted: " . $bitcoin->can_connect() . "\n");
-  $monitoring->setStatus($cron_name . "_active", "yesno", 0); 
-  $monitoring->setStatus($cron_name . "_message", "message", "Unable to connect to RPC server");
-  $monitoring->setStatus($cron_name . "_status", "okerror", 1); 
-  exit(1);
+  $log->logFatal('Unable to connect to RPC server backend');
+  $monitoring->endCronjob($cron_name, 'E0006', 1, true);
 }
 
 // We support some dynamic reward targets but fall back to our fixed value