From: Kern Sibbald <kern@sibbald.com>
Date: Sat, 13 Sep 2008 12:50:20 +0000 (+0000)
Subject: Clarify that canceling can take several hours
X-Git-Tag: Release-3.0.0~988
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=843cd887d662624e93399520c0186d67e4e76764;p=bacula%2Fdocs

Clarify that canceling can take several hours
---

diff --git a/docs/manuals/en/console/bconsole.tex b/docs/manuals/en/console/bconsole.tex
index 6921dd67..53422f94 100644
--- a/docs/manuals/en/console/bconsole.tex
+++ b/docs/manuals/en/console/bconsole.tex
@@ -334,8 +334,13 @@ The following commands are currently implemented:
    you to choose one.
 
    Once a Job is marked to be canceled, it may take a bit of time
-   (generally within a minute) before it actually terminates, depending on
-   what operations it is doing.
+   (generally within a minute but up to two hours) before the Job actually 
+   terminates, depending on what operations it is doing.
+   Don't be surprised that you receive a Job not found message. That just
+   means that one of the three daemons had already canceled the job.
+   Messages numbered in the 1000's are from the Director, 2000's are from
+   the File daemon and 3000's from the Storage daemon.
+
 
 \item [{create [pool=\lt{}pool-name\gt{}]}]
    \index[general]{create pool}