From: Thomas Glatthor Date: Wed, 12 Sep 2007 08:49:52 +0000 (+0000) Subject: "autochanger script specifed on {\bf Changer Device} statement." X-Git-Tag: Release-3.0.0~2541 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=67a7c43061b8c27a0ec43ea584fcc92c3c8ea2ac;p=bacula%2Fdocs "autochanger script specifed on {\bf Changer Device} statement." changed Device to Command, add one missing ")" --- diff --git a/docs/manual/autochangers.tex b/docs/manual/autochangers.tex index b37484ae..1611cfb5 100644 --- a/docs/manual/autochangers.tex +++ b/docs/manual/autochangers.tex @@ -712,7 +712,7 @@ or one number per line for each slot that is occupied in your changer, and the number should be terminated by a colon ({\bf :}). If your changer has barcodes, the barcode will follow the colon. If an error message is printed, you must resolve the problem (e.g. try a different SCSI control device name -if {\bf /dev/sg0} is incorrect. For example, on FreeBSD systems, the +if {\bf /dev/sg0} is incorrect). For example, on FreeBSD systems, the autochanger SCSI control device is generally {\bf /dev/pass2}. \item [/etc/bacula/mtx-changer \ /dev/sg0 \ slots ] @@ -948,7 +948,7 @@ prevent Bacula from attempting to write on the Volume. \index[general]{Bacula Autochanger Interface } Bacula calls the autochanger script that you specify on the {\bf Changer -Device} statement. Normally this script will be the {\bf mtx-changer} script +Command} statement. Normally this script will be the {\bf mtx-changer} script that we provide, but it can in fact be any program. The only requirement for the script is that it must understand the commands that Bacula uses, which are {\bf loaded}, {\bf load}, {\bf