Final changes

diff --git a/docs/manual/autochangerres.tex b/docs/manual/autochangerres.tex
index 9798e08cfe21d9fa4605148414c6169ddabd69ab..7cd3b87b9231e3e3e272b92f5c638bcdc578bcd6 100644 (file)
--- a/docs/manual/autochangerres.tex
+++ b/docs/manual/autochangerres.tex
@@ -8,6 +8,15 @@ autochangers by grouping one or more Device resources
 into one unit called an autochanger in Bacula (often referred to
 as a "tape library" by autochanger manufacturers).
 
+If you have an Autochanger, and you want it to function correctly,
+you {\bf must} have an Autochanger resource in your Storage
+conf file, and your Director's Storage directives that want to
+use an Autochanger {\bf must} refer to the Autochanger resource name.
+In previous versions of Bacula, the Director's Storage directives
+referred directly to Device resources that were autochangers.     
+In version 1.38.0 and later, referring directly to Device resources
+will not work for Autochangers.
+
 \begin{description}
 \item [Name = \lt{}Autochanger-Name\gt{}]
    \index[sd]{Name}
@@ -41,7 +50,7 @@ as a "tape library" by autochanger manufacturers).
    automatically change volumes as required by {\bf Bacula}.  Most frequently,
    you will specify the Bacula supplied {\bf mtx-changer}  script as follows.
    If it is specified here, it need not be specified in the Device
-   resource. If it is specified in the Device resource, it will take
+   resource. If it is also specified in the Device resource, it will take
    precedence over the one specified in the Autochanger resource.
 
 \end{description}
@@ -95,7 +104,7 @@ Autoselect = no
 
 to the Device resource for that drive. In that case, Bacula will not automatically
 select that drive when accessing the Autochanger. You can, still use the drive
-by referencing it by the Device name rather than the Autochanger name. An example
+by referencing it by the Device name directly rather than the Autochanger name. An example
 of such a definition is shown above for the Device DDS-4-3, which will not be
 selected when the name DDS-4-changer is used in a Storage definition, but will
 be used if DDS-4-3 is used.

diff --git a/docs/manual/storedconf.tex b/docs/manual/storedconf.tex
index 5f201da50c9e85dbd42a87c86bc3b46ec5b58a94..0537fadfc07e75e131f436fd89a6923f156ef215 100644 (file)
--- a/docs/manual/storedconf.tex
+++ b/docs/manual/storedconf.tex
@@ -392,8 +392,10 @@ specified within the Device resource are specific to the Device.
 \item [Autochanger = {\it Yes|No}]
    \index[sd]{Autochanger}
    \index[sd]{Directive!Autochanger}
-   If {\bf Yes}, this device belongs to an automatic tape changer, and  you should also
-   specify a {\bf Changer Device} as well as  a {\bf Changer Command}.  If {\bf
+   If {\bf Yes}, this device belongs to an automatic tape changer, and you
+   must specify an {\bf Autochanger} resource that points to the {\bf
+   Device} resources.  You must also specify a 
+   {\bf Changer Device}.  If the Autochanger direcive is set to {\bf
    No} (default), the volume must be manually changed.  You should also
    have an identical directive to the  
    \ilink{Storage resource}{Autochanger1}  in the Director's
@@ -420,7 +422,11 @@ specified within the Device resource are specific to the Device.
    \index[sd]{Changer Command}
    \index[sd]{Directive!Changer Command}
    The {\bf name-string} specifies an external program to be called  that will
-   automatically change volumes as required by {\bf Bacula}.  Most frequently,
+   automatically change volumes as required by {\bf Bacula}.  Normally,
+   this directive will be specified only in the {\bf AutoChanger} resource,
+   which is then used for all devices.  However, you may also specify
+   the different {\bf Changer Commands} in each Device specification.
+   Most frequently,
    you will specify the Bacula supplied {\bf mtx-changer}  script as follows:  
 
 \footnotesize
@@ -482,15 +488,16 @@ bacula-sd  Alert: TapeAlert[32]: Interface: Problem with SCSI interface
    The {\bf Drive Index} that you specify is passed to the  {\bf mtx-changer}
    script and is thus passed to the {\bf mtx}  program. By default, the Drive
    Index is zero, so if you have only  one drive in your autochanger, everything
-   will work normally.  However, if you have multiple drives, you may specify two
-   Bacula  Device resources. The first will either set Drive Index to zero,  or
+   will work normally.  However, if you have multiple drives, you must specify t
+   multiple Bacula  Device resources (one for each drive).
+   The first will either set Drive Index to zero,  or
    leave it unspecified, and the second Device Resource should  contain a Drive
-   Index set to 1. This will then permit you to  use two or more drives in your
-   autochanger. However, you must ensure  that Bacula does not request the same
-   Volume on both drives  at the same time. You may also need to modify the
-   mtx-changer  script to do locking so that two jobs don't attempt to use  the
-   autochanger at the same time. An example script can  be found in {\bf
-   examples/autochangers/locking-mtx-changer}.
+   Index set to 1, and so on. This will then permit you to  use two or more drives in your
+   autochanger. As of Bacula version 1.38.0, using the {\bf Autochanger}
+   resource, Bacula will automatically ensure that only one drive at a
+   time uses the autochanger script, so you no longer need locking scripts
+   as in the past -- the default mtx-changer script works for any number
+   of drives.
 
 \item [Autoselect = {\it Yes|No}]
    \index[sd]{Autoselect}
@@ -1009,10 +1016,14 @@ apply to removable filesystems such as USB in addition to DVD.
 
 \end{description}
 
+%% This pulls in the Autochanger resource from another file.
 \label{AutochangerRes}
 \label{AutochangerResource1}
 \input{autochangerres}
 
+
+
+
 \subsection*{Capabilities}
 \index[general]{Capabilities}
 \addcontentsline{toc}{subsection}{Capabilities}