From 9d0a7a32fb5de2085db9f02453f10527d498adc8 Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Fri, 10 Aug 2007 10:13:21 +0000 Subject: [PATCH] Apply dirdconf patch supplied by Marc Schiffbauer --- docs/manual/dirdconf.tex | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/docs/manual/dirdconf.tex b/docs/manual/dirdconf.tex index 7cf6adad..fd274152 100644 --- 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. -- 2.39.5