Apply dirdconf patch supplied by Marc Schiffbauer

diff --git a/docs/manual/dirdconf.tex b/docs/manual/dirdconf.tex
index 7cf6adad4ccb6de7f903f33016dfdb0ec0be8b75..fd274152afdb2b4b3d3c7081d51667b3bcda3fb8 100644 (file)
--- a/docs/manual/dirdconf.tex
+++ b/docs/manual/dirdconf.tex
@@ -1522,9 +1522,9 @@ RunScript {
 \item [Priority = \lt{}number\gt{}]
    \index[dir]{Priority}
    \index[dir]{Directive!Priority}
-   This directive permits you to control the order in which your jobs run
-   by specifying a positive non-zero number.  The higher the number, the
-   lower the job priority.  Assuming you are not running concurrent jobs,
+   This directive permits you to control the order in which your jobs are
+   being run by specifying a positive non-zero number. The higher the number,
+   the lower the job priority. Assuming you are not running concurrent jobs,
    all queued jobs of priority 1 will run before queued jobs of priority 2
    and so on, regardless of the original scheduling order.
 
@@ -1539,12 +1539,8 @@ RunScript {
    keep these points in mind:
 
 \begin{itemize}
-\item To run concurrent jobs, you must set Maximum Concurrent Jobs = 2 in five
-   or six distinct places: in bacula-dir.conf in the Director, the Job, the
-   Client, the Storage resources; in bacula-fd in the FileDaemon (or
-   Client) resource, and in bacula-sd.conf in the Storage resource.  If any
-   one is missing, it will throttle the jobs to one at a time. You may, of
-   course, set the Maximum Concurrent Jobs to more than 2.
+\item See \ilink{Running Concurrent Jobs}{ConcurrentJobs} on how to setup
+   concurrent jobs.
 
 \item Bacula concurrently runs jobs of only one priority at a time.  It
    will not simultaneously run a priority 1 and a priority 2 job.