From 0356b3d1997b7a5bb1d8aa8ab8de35661786f994 Mon Sep 17 00:00:00 2001 From: Eric Bollengier Date: Mon, 6 Jan 2014 10:05:18 +0100 Subject: [PATCH] Fix #136 about missing documentation of the Priority field in Schedule --- docs/manuals/en/main/dirdconf.tex | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/docs/manuals/en/main/dirdconf.tex b/docs/manuals/en/main/dirdconf.tex index 29c2d554..322730aa 100644 --- 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 -- 2.39.5