From: Eric Bollengier <eric@baculasystems.com>
Date: Wed, 25 Jan 2012 08:43:53 +0000 (+0100)
Subject: Disable usage of JS_Warning waiting for a more complete implementation
X-Git-Tag: Release-7.0.0~310
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=2c6680d8ca340d7dce9e9d21a94385f42369bda0;p=bacula%2Fbacula

Disable usage of JS_Warning waiting for a more complete implementation
---

diff --git a/bacula/src/dird/backup.c b/bacula/src/dird/backup.c
index c2321aacf8..8f0f7ec4e5 100644
--- a/bacula/src/dird/backup.c
+++ b/bacula/src/dird/backup.c
@@ -607,10 +607,17 @@ void backup_cleanup(JCR *jcr, int TermCode)
    memset(&mr, 0, sizeof(mr));
    memset(&cr, 0, sizeof(cr));
 
+#ifdef xxxx
+   /* The current implementation of the JS_Warning status is not
+    * completed. SQL part looks to be ok, but the code is using
+    * JS_Terminated almost everywhere instead of (JS_Terminated || JS_Warning)
+    * as we do with is_canceled()
+    */
    if (jcr->getJobStatus() == JS_Terminated && 
         (jcr->JobErrors || jcr->SDErrors || jcr->JobWarnings)) {
       TermCode = JS_Warnings;
    }
+#endif
          
    update_job_end(jcr, TermCode);