Fix #136 about missing documentation of the Priority field in Schedule

diff --git a/docs/manuals/en/main/dirdconf.tex b/docs/manuals/en/main/dirdconf.tex
index 29c2d5548fe6793db341affcfb4a3a7ea20af75e..322730aa028aad4c5b0d04a8d6cf0087299929e0 100644 (file)
--- a/docs/manuals/en/main/dirdconf.tex
+++ b/docs/manuals/en/main/dirdconf.tex
@@ -2144,6 +2144,25 @@ incremental  backup.
    otherwise, when the last job has finished one part will remain in the
    spool file and restore may or may not work.
 
+\item [Priority = \lt{}number\gt{}]
+   \index[dir]{Priority}
+   \index[dir]{Directive!Priority}
+   This directive permits you to control the order in which your jobs will
+   be 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.
+
+   The priority only affects waiting jobs that are queued to run, not jobs
+   that are already running.  If one or more jobs of priority 2 are already
+   running, and a new job is scheduled with priority 1, the currently
+   running priority 2 jobs must complete before the priority 1 job is
+   run, unless Allow Mixed Priority is set.
+
+   The default priority is 10.
+
+   See \vref{Director:Job:Priority} for more information.
+
 \end{description}
 
 {\bf Date-time-specification} determines when the  Job is to be run. The