From 51d6ee01b9fe93c660b856b2cd6226eda2dbcaa0 Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Sun, 9 Nov 2014 16:10:53 +0100 Subject: [PATCH] Eliminate DVD specific directives -- WritePart ... --- docs/latex/external-references.tex | 1 + docs/manuals/en/main/dirdconf.tex | 56 ++++++++++++++--------------- docs/manuals/en/main/storedconf.tex | 4 +-- 3 files changed, 31 insertions(+), 30 deletions(-) diff --git a/docs/latex/external-references.tex b/docs/latex/external-references.tex index 758851cf..11769895 100644 --- a/docs/latex/external-references.tex +++ b/docs/latex/external-references.tex @@ -54,6 +54,7 @@ \externaldocument[main-]{../main/bootstrap} \externaldocument[main-]{../main/autochangers} \externaldocument[main-]{../main/migration} +\externaldocument[main-]{../main/images} \externaldocument[main-]{../main/supporteddrives} \externaldocument[main-]{../main/restore} \externaldocument[main-]{../main/postgresql} diff --git a/docs/manuals/en/main/dirdconf.tex b/docs/manuals/en/main/dirdconf.tex index 582a21a6..3675b948 100644 --- a/docs/manuals/en/main/dirdconf.tex +++ b/docs/manuals/en/main/dirdconf.tex @@ -1835,25 +1835,25 @@ correct order, and that your priority scheme will be respected. the running jobs finishes. However, new priority 10 jobs will not be run until the priority 5 job has finished. -\label{WritePartAfterJob} -\item [Write Part After Job = \lt{}yes\vb{}no\gt{}] -\index[dir]{Write Part After Job} -\index[dir]{Directive!Write Part After Job} - This directive is only implemented in version 1.37 and later. - If this directive is set to {\bf yes} (default {\bf no}), a new part file - will be created after the job is finished. - - It should be set to {\bf yes} when writing to devices that require mount - (for example DVD), so you are sure that the current part, containing - this job's data, is written to the device, and that no data is left in - the temporary file on the hard disk. However, on some media, like DVD+R - and DVD-R, a lot of space (about 10Mb) is lost every time a part is - written. So, if you run several jobs each after another, you could set - this directive to {\bf no} for all jobs, except the last one, to avoid - wasting too much space, but to ensure that the data is written to the - medium when all jobs are finished. - - This directive is ignored with tape and FIFO devices. +%% \label{WritePartAfterJob} +%% \item [Write Part After Job = \lt{}yes\vb{}no\gt{}] +%% \index[dir]{Write Part After Job} +%% \index[dir]{Directive!Write Part After Job} +%% This directive is only implemented in version 1.37 and later. +%% If this directive is set to {\bf yes} (default {\bf no}), a new part file +%% will be created after the job is finished. + +%% It should be set to {\bf yes} when writing to devices that require mount +%% (for example DVD), so you are sure that the current part, containing +%% this job's data, is written to the device, and that no data is left in +%% the temporary file on the hard disk. However, on some media, like DVD+R +%% and DVD-R, a lot of space (about 10Mb) is lost every time a part is +%% written. So, if you run several jobs each after another, you could set +%% this directive to {\bf no} for all jobs, except the last one, to avoid +%% wasting too much space, but to ensure that the data is written to the +%% medium when all jobs are finished. + +%% This directive is ignored with tape and FIFO devices. \end{description} @@ -1995,15 +1995,15 @@ incremental backup. cases. -\item [WritePartAfterJob=yes\vb{}no] - \index[dir]{WritePartAfterJob} - \index[dir]{Directive!WritePartAfterJob} - tells Bacula to request the Storage daemon to write the current part - file to the device when the job is finished (see \ilink{Write Part After Job directive in the Job resource}{WritePartAfterJob}). Please note, - this directive is implemented only in version 1.37 and later. The - default is yes. We strongly recommend that you keep this set to yes - otherwise, when the last job has finished one part will remain in the - spool file and restore may or may not work. +%% \item [WritePartAfterJob=yes\vb{}no] +%% \index[dir]{WritePartAfterJob} +%% \index[dir]{Directive!WritePartAfterJob} +%% tells Bacula to request the Storage daemon to write the current part +%% file to the device when the job is finished (see \ilink{Write Part After Job directive in the Job resource}{WritePartAfterJob}). Please note, +%% this directive is implemented only in version 1.37 and later. The +%% default is yes. We strongly recommend that you keep this set to yes +%% otherwise, when the last job has finished one part will remain in the +%% spool file and restore may or may not work. \end{description} diff --git a/docs/manuals/en/main/storedconf.tex b/docs/manuals/en/main/storedconf.tex index ac4b39d4..a0e44b0c 100644 --- a/docs/manuals/en/main/storedconf.tex +++ b/docs/manuals/en/main/storedconf.tex @@ -1082,8 +1082,8 @@ apply to removable filesystems such as USB. USB unless they are automounted, and to {\bf no} for all other devices (tapes/files). This directive indicates if the device requires to be mounted to be read, and if it must be written in a special way. If it - set, {\bf Mount Point}, {\bf Mount Command}, {\bf Unmount Command} and - {\bf Write Part Command} directives must also be defined. + set, {\bf Mount Point}, {\bf Mount Command}, and {\bf Unmount Command} + directives must also be defined. \item [Mount Point = {\it directory}] \index[sd]{Mount Point} -- 2.39.5