From 2a2f34a4fd76dbf1f79ea2c7c878436c0c9628e2 Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Thu, 28 Dec 2006 16:20:39 +0000 Subject: [PATCH] Fix indexing syntax errors --- docs/developers/version.tex | 2 +- docs/manual-de/version.tex | 2 +- docs/manual/autochangers.tex | 6 +++--- docs/manual/console.tex | 1 - docs/manual/disk.tex | 5 ++--- docs/manual/gpl.tex | 1 - docs/manual/internaldb.tex | 7 +++---- docs/manual/lesser.tex | 2 +- docs/manual/migration.tex | 8 +++++++- docs/manual/mysql.tex | 1 - docs/manual/progs.tex | 7 ++----- docs/manual/quickstart.tex | 5 ++--- docs/manual/rpm-faq.tex | 1 - docs/manual/sqlite.tex | 2 -- docs/manual/state.tex | 1 - docs/manual/stunnel.tex | 3 --- docs/manual/tapetesting.tex | 35 +++++++++++------------------------ docs/manual/tips.tex | 3 +-- docs/manual/tutorial.tex | 12 ++++-------- docs/manual/version.tex | 2 +- docs/manual/win32.tex | 2 -- 21 files changed, 39 insertions(+), 69 deletions(-) diff --git a/docs/developers/version.tex b/docs/developers/version.tex index 146adc4c..a7e70623 100644 --- a/docs/developers/version.tex +++ b/docs/developers/version.tex @@ -1 +1 @@ -1.39.32 (20 December 2006) +1.39.33 (28 December 2006) diff --git a/docs/manual-de/version.tex b/docs/manual-de/version.tex index 146adc4c..a7e70623 100644 --- a/docs/manual-de/version.tex +++ b/docs/manual-de/version.tex @@ -1 +1 @@ -1.39.32 (20 December 2006) +1.39.33 (28 December 2006) diff --git a/docs/manual/autochangers.tex b/docs/manual/autochangers.tex index 2f27c22a..57ac46aa 100644 --- a/docs/manual/autochangers.tex +++ b/docs/manual/autochangers.tex @@ -634,10 +634,10 @@ Please see the autochanger testing. \label{AutochangerTesting} -\section{Testing Autochanger and Adapting mtx-changer} +\section{Testing Autochanger and Adapting mtx-changer script} \index[general]{Testing the Autochanger } -\index[general]{Adapting Your mtx-changer } -mtx-changer} +\index[general]{Adapting Your mtx-changer script} + Before attempting to use the autochanger with Bacula, it is preferable to "hand-test" that the changer works. To do so, we suggest you do the diff --git a/docs/manual/console.tex b/docs/manual/console.tex index 02652599..920721a9 100644 --- a/docs/manual/console.tex +++ b/docs/manual/console.tex @@ -1425,7 +1425,6 @@ regression test might be: \section{Running the Console from a Shell Script} \index[general]{Script!Running the Console Program from a Shell} \index[general]{Running the Console Program from a Shell Script} -Script} You can automate many Console tasks by running the console program from a shell script. For example, if you have created a file containing the following diff --git a/docs/manual/disk.tex b/docs/manual/disk.tex index ee2d7506..1f3358ed 100644 --- a/docs/manual/disk.tex +++ b/docs/manual/disk.tex @@ -225,9 +225,8 @@ records. \label{Recycling1} \subsection{Restricting the Number of Volumes and Recycling} -\index[general]{Recycling!Restricting the Number of Volumes and } -\index[general]{Restricting the Number of Volumes and Recycling } -Recycling} +\index[general]{Recycling!Restricting the Number of Volumes and Recycling} +\index[general]{Restricting the Number of Volumes and Recycling} Automatic labeling discussed above brings up the problem of Volume management. With the above scheme, a new Volume will be created every day. If you have not diff --git a/docs/manual/gpl.tex b/docs/manual/gpl.tex index c6441ab5..a4db8126 100644 --- a/docs/manual/gpl.tex +++ b/docs/manual/gpl.tex @@ -336,7 +336,6 @@ END OF TERMS AND CONDITIONS \label{SEC4} \index[general]{Programs!How to Apply These Terms to Your New } \index[general]{How to Apply These Terms to Your New Programs } -Programs} If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software diff --git a/docs/manual/internaldb.tex b/docs/manual/internaldb.tex index 514d4f03..fb0f865b 100644 --- a/docs/manual/internaldb.tex +++ b/docs/manual/internaldb.tex @@ -1,14 +1,13 @@ %% %% -\section*{The Bacula internal database is no longer supported, please do not +\section*{The internal database is not supported, please do not use it.} \label{_ChapterStart42} -\index[general]{Use it!Bacula internal database is no longer supported please +\index[general]{Use it!The internal database is not supported please do not } -\index[general]{Bacula internal database is no longer supported, please do not +\index[general]{The internal database is not supported, please do not use it. } -supported, please do not use it.} \section{Internal Bacula Database} \index[general]{Internal Bacula Database } diff --git a/docs/manual/lesser.tex b/docs/manual/lesser.tex index 2f58cb26..5bee83d3 100644 --- a/docs/manual/lesser.tex +++ b/docs/manual/lesser.tex @@ -508,7 +508,7 @@ END OF TERMS AND CONDITIONS \label{SEC45} \index[general]{Libraries!How to Apply These Terms to Your New } \index[general]{How to Apply These Terms to Your New Libraries } -Libraries} + If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can diff --git a/docs/manual/migration.tex b/docs/manual/migration.tex index 1a5d87c1..794ae744 100644 --- a/docs/manual/migration.tex +++ b/docs/manual/migration.tex @@ -262,7 +262,9 @@ are used to define a Migration job. marked, Full, Used, or Error. Volumes that are still marked Append will not be considered for migration. This prevents Bacula from attempting to read the Volume at - the same time it is writing it. + the same time it is writing it. It also reduces other deadlock + situations, as well as avoids the problem that you migrate a + Volume and later find new files appended to that Volume. \item As noted above, for the Migration High Bytes, the calculation of the bytes to migrate is somewhat approximate. @@ -307,6 +309,10 @@ are used to define a Migration job. all reference the same Volume will run sequentially. This can be a potential bottle neck and does not scale very well to large numbers of jobs. + +\item Only migration of Selection Types of Job and Volume have + been carefully tested. All the other migration methods (time, + occupancy, smallest, oldest, ...) need additional testing. \end{itemize} diff --git a/docs/manual/mysql.tex b/docs/manual/mysql.tex index 6ab5ec5a..2ad4fa98 100644 --- a/docs/manual/mysql.tex +++ b/docs/manual/mysql.tex @@ -119,7 +119,6 @@ Installation. \section{Installing and Configuring MySQL -- Phase II} \index[general]{Installing and Configuring MySQL -- Phase II } \index[general]{Phase II!Installing and Configuring MySQL -- } -II} At this point, you should have built and installed MySQL, or already have a running MySQL, and you should have configured, built and installed {\bf diff --git a/docs/manual/progs.tex b/docs/manual/progs.tex index 1e71dce1..985462eb 100644 --- a/docs/manual/progs.tex +++ b/docs/manual/progs.tex @@ -561,7 +561,6 @@ normal Bacula console commands. \subsection{Using bscan to Compare a Volume to an existing Catalog} \index[general]{Catalog!Using bscan to Compare a Volume to an existing} \index[general]{Using bscan to Compare a Volume to an existing Catalog} -existing Catalog} If you wish to compare the contents of a Volume to an existing catalog without changing the catalog, you can safely do so if and only if you do {\bf not} @@ -571,9 +570,8 @@ as they should be, so we don't particularly recommend this mode other than for testing. \subsection{Using bscan to Recreate a Catalog from a Volume} -\index[general]{Volume!Using bscan to Recreate a Catalog from a} +\index[general]{Volume!Using bscan to Recreate a Catalog from a Volume} \index[general]{Using bscan to Recreate a Catalog from a Volume} -Volume} This is the mode for which {\bf bscan} is most useful. You can either {\bf bscan} into a freshly created catalog, or directly into your existing catalog @@ -689,8 +687,7 @@ against it and get valid results. \subsection{Using bscan to Correct the Volume File Count} \index[general]{Using bscan to Correct the Volume File Count} -\index[general]{Count!Using bscan to Correct the Volume File} -Count} +\index[general]{Count!Using bscan to Correct the Volume File Count} If the Storage daemon crashes during a backup Job, the catalog will not be properly updated for the Volume being used at the time of the crash. This diff --git a/docs/manual/quickstart.tex b/docs/manual/quickstart.tex index ce600ef4..0f688ade 100644 --- a/docs/manual/quickstart.tex +++ b/docs/manual/quickstart.tex @@ -300,9 +300,8 @@ conf file name). \label{TapeTesting} \section{Testing Compatibility with Your Tape Drive} -\index[general]{Drive!Testing Bacula Compatibility with Your Tape } -\index[general]{Testing Bacula Compatibility with Your Tape Drive } -Drive} +\index[general]{Drive!Testing Bacula Compatibility with Your Tape} +\index[general]{Testing Bacula Compatibility with Your Tape Drive} Before spending a lot of time on Bacula only to find that it doesn't work with your tape drive, please read the \ilink{btape -- Testing Your Tape diff --git a/docs/manual/rpm-faq.tex b/docs/manual/rpm-faq.tex index 2b196685..3ce3901d 100644 --- a/docs/manual/rpm-faq.tex +++ b/docs/manual/rpm-faq.tex @@ -5,7 +5,6 @@ \label{_ChapterStart34} \index[general]{FAQ!Bacula\textsuperscript{\textregistered} - RPM Packaging } \index[general]{Bacula\textsuperscript{\textregistered} - RPM Packaging FAQ } -Packaging FAQ} \begin{enumerate} \item diff --git a/docs/manual/sqlite.tex b/docs/manual/sqlite.tex index ac87d0e1..a95b386f 100644 --- a/docs/manual/sqlite.tex +++ b/docs/manual/sqlite.tex @@ -9,7 +9,6 @@ \section{Installing and Configuring SQLite -- Phase I} \index[general]{Phase I!Installing and Configuring SQLite -- } \index[general]{Installing and Configuring SQLite -- Phase I } -I} If you use the {\bf ./configure \verb:--:with-sqlite} statement for configuring {\bf Bacula}, you will need SQLite version 2.8.16 or later installed. Our standard @@ -56,7 +55,6 @@ include {\bf \verb:--:with-sqlite}. \label{phase2} \index[general]{Phase II!Installing and Configuring SQLite -- } \index[general]{Installing and Configuring SQLite -- Phase II } -II} This phase is done {\bf after} you have run the {\bf ./configure} command to configure {\bf Bacula}. diff --git a/docs/manual/state.tex b/docs/manual/state.tex index 6fdb965d..67ec18d3 100644 --- a/docs/manual/state.tex +++ b/docs/manual/state.tex @@ -138,7 +138,6 @@ In other words, what is and what is not currently implemented and functional. \section{Advantages Over Other Backup Programs} \index[general]{Advantages of Bacula Over Other Backup Programs } \index[general]{Programs!Advantages of Bacula Over Other Backup } - Programs} \begin{itemize} \item Since there is a client for each machine, you can backup diff --git a/docs/manual/stunnel.tex b/docs/manual/stunnel.tex index 461421c5..937e0c4c 100644 --- a/docs/manual/stunnel.tex +++ b/docs/manual/stunnel.tex @@ -4,7 +4,6 @@ \chapter{Using Stunnel to Encrypt Communications} \label{_ChapterStart6} \index[general]{Using Stunnel to Encrypt Communications to Clients } -Clients} Prior to version 1.37, Bacula did not have built-in communications encryption. Please see the \ilink {TLS chapter}{CommEncryption} if you are using Bacula @@ -164,7 +163,6 @@ well. \section{Stunnel Configuration for the Data Channel} \index[general]{Stunnel Configuration for the Data Channel } -Channel} In the diagram above, we see above Stunnel 2 that we use stunnel-fd2.conf on the client. A pretty much minimal config file would look like the following: @@ -333,7 +331,6 @@ localhost:29102 instead of directly to the client. \section{Stunnel Configuration for the Control Channel} \index[general]{Config Files for stunnel to Encrypt the Control Channel } -Control Channel} The stunnel config file, stunnel-dir.conf, for the Director's machine would look like the following: diff --git a/docs/manual/tapetesting.tex b/docs/manual/tapetesting.tex index cb9475a0..2894535e 100644 --- a/docs/manual/tapetesting.tex +++ b/docs/manual/tapetesting.tex @@ -545,13 +545,9 @@ medium, and Bacula will keep track of the file number itself. \end{itemize} \label{IncorrectBlocks} -\subsection{Incorrect Number of Blocks or Positioning Errors during btape -Testing} -\index[general]{Testing!Incorrect Number of Blocks or Positioning Errors -during btape} -\index[general]{Incorrect Number of Blocks or Positioning Errors during btape -Testing} -Errors during btape Testing} +\subsection{Incorrect Number of Blocks or Positioning Errors} +\index[general]{Testing!Incorrect Number of Blocks or Positioning Errors} +\index[general]{Incorrect Number of Blocks or Positioning Errors} {\bf Bacula's} preferred method of working with tape drives (sequential devices) is to run in variable block mode, and this is what is set by default. @@ -609,8 +605,6 @@ To recover files from tapes written in fixed block mode, see below. \subsection{Ensuring that the Tape Modes Are Properly Set -- {\bf Linux Only}} \index[general]{Ensuring that the Tape Modes Are Properly Set -- Linux Only} -\index[general]{Only!Ensuring that the Tape Modes Are Properly Set -- Linux} -Set -- Linux Only} If you have a modern SCSI tape drive and you are having problems with the {\bf test} command as noted above, it may be that some program has set one or more @@ -687,13 +681,9 @@ OSes permit setting variable block mode, but some OSes do not permit setting the other modes that Bacula needs to function properly. \label{compression} -\subsection{Checking and Setting Tape Hardware Compression and Blocking -Size} -\index[general]{Checking and Setting Tape Hardware Compression and Blocking -Size} -\index[general]{Size!Checking and Setting Tape Hardware Compression and -Blocking} -Compression and Blocking Size} +\subsection{Tape Hardware Compression and Blocking Size} +\index[general]{Tape Hardware Compression and Blocking Size} +\index[general]{Size!Tape Hardware Compression and Blocking Size} As far as I can tell, there is no way with the {\bf mt} program to check if your tape hardware compression is turned on or off. You can, however, turn it @@ -917,9 +907,8 @@ Backward Space Record = yes. \subsection{Finding your Tape Drives and Autochangers on FreeBSD} -\index[general]{FreeBSD!Finding your Tape Drives and Autochangers} -\index[general]{Finding your Tape Drives and Autochangers on FreeBSD} -Autochangers on FreeBSD} +\index[general]{FreeBSD!Finding Tape Drives and Autochangers} +\index[general]{Finding Tape Drives and Autochangers on FreeBSD} On FreeBSD, you can do a {\bf camcontrol devlist} as root to determine what drives and autochangers you have. For example, @@ -950,7 +939,6 @@ tapeinfo -f /dev/pass2 \subsection{Using the OnStream driver on Linux Systems} \index[general]{Using the OnStream driver on Linux Systems} \index[general]{Systems!Using the OnStream driver on Linux} -Systems} Bacula version 1.33 (not 1.32x) is now working and ready for testing with the OnStream kernel osst driver version 0.9.14 or above. Osst is available from: @@ -1001,6 +989,7 @@ Device { \section{Hardware Compression on EXB-8900} \index[general]{Hardware Compression on EXB-8900} \index[general]{EXB-8900!Hardware Compression} + To active, check, or disable the hardware compression feature on an EXB-8900, use the exabyte MammothTool. You can get it here: \elink{http://www.exabyte.com/support/online/downloads/index.cfm} @@ -1012,8 +1001,7 @@ options for a small reference. \label{fill} \subsection{Using btape to Simulate Filling a Tape} \index[general]{Using btape to Simulate Filling a Tape} -\index[general]{Tape!Using btape to Simulate Filling a} -Tape} +\index[general]{Tape!Using btape to Simulate Filling} Because there are often problems with certain tape drives or systems when end of tape conditions occur, {\bf btape} has a special command {\bf fill} that @@ -1040,8 +1028,7 @@ Bacula. \label{RecoveringFiles} \section{Recovering Files Written With Fixed Block Sizes} -\index[general]{Recovering Files Written to Tape With Fixed Block Sizes} -Block Sizes} +\index[general]{Recovering Files Written With Fixed Block Sizes} If you have been previously running your tape drive in fixed block mode (default 512) and Bacula with variable blocks (default), then in version diff --git a/docs/manual/tips.tex b/docs/manual/tips.tex index 8bf6bb6f..77da536e 100644 --- a/docs/manual/tips.tex +++ b/docs/manual/tips.tex @@ -745,8 +745,7 @@ myself that the backups would all complete without my intervention. \section{Exclude Files on Windows Regardless of Case} \label{Case} -\index[general]{Exclude Files on Windows Regardless of Case } -Case} +\index[general]{Exclude Files on Windows Regardless of Case} % TODO: should this be put in the win32 chapter? % TODO: should all these tips be placed in other chapters? diff --git a/docs/manual/tutorial.tex b/docs/manual/tutorial.tex index 9c0efd9b..3d78b999 100644 --- a/docs/manual/tutorial.tex +++ b/docs/manual/tutorial.tex @@ -121,9 +121,8 @@ explains how you can install scripts that will automatically restart the daemons when the system starts. \section{Using the Director to Query and Start Jobs} -\index[general]{Jobs!Interacting with the Director to Query or Start } -\index[general]{Interacting with the Director to Query or Start Jobs } -Start Jobs} +\index[general]{Jobs!Querying or Starting Jobs} +\index[general]{Querying or starting Jobs} % TODO: section name is too long; maybe use "Using the Console Program" ?? To communicate with the director and to query the state of Bacula or run jobs, @@ -811,7 +810,6 @@ Then make sure that the Address parameter in the Storage resource is set to the fully qualified domain name and not to something like "localhost". The address specified is sent to the File daemon (client) and it must be a fully qualified domain name. If you pass something like "localhost" it will not -% TODO: s/will/may/ ?? resolve correctly and will result in a time out when the File daemon fails to connect to the Storage daemon. @@ -1067,7 +1065,6 @@ permit non-root access. MySQL and PostgreSQL can be installed and run with any userid; root privilege is not necessary. \section{Patience When Starting Daemons or Mounting Blank Tapes} -Mounting Blank Tapes} When you start the Bacula daemons, the Storage daemon attempts to open all defined storage devices and verify the currently mounted Volume (if @@ -1087,9 +1084,8 @@ consequence, you are again urged to have patience when inserting blank tapes. Let the device settle down before attempting to access it. \section{Difficulties Connecting from the FD to the SD} -\index[general]{Difficulties Connecting from the FD to the SD } -\index[general]{SD!Difficulties Connecting from the FD to the } -SD} +\index[general]{Difficulties Connecting from the FD to the SD} +\index[general]{SD!Difficulties Connecting from the FD to the SD} If you are having difficulties getting one or more of your File daemons to connect to the Storage daemon, it is most likely because you have not used a diff --git a/docs/manual/version.tex b/docs/manual/version.tex index 146adc4c..a7e70623 100644 --- a/docs/manual/version.tex +++ b/docs/manual/version.tex @@ -1 +1 @@ -1.39.32 (20 December 2006) +1.39.33 (28 December 2006) diff --git a/docs/manual/win32.tex b/docs/manual/win32.tex index fc12da5d..706568c5 100644 --- a/docs/manual/win32.tex +++ b/docs/manual/win32.tex @@ -603,7 +603,6 @@ Thanks to Georger Araujo for the above information. \section{Windows Ownership and Permissions Problems} \index[general]{Problems!Windows Ownership and Permissions} \index[general]{Windows Ownership and Permissions Problems} -Problems} If you restore files backed up from WinNT/XP/2K to an alternate directory, Bacula may need to create some higher level directories that were not saved @@ -719,7 +718,6 @@ please report your results to the Bacula email list. \section{Considerations for Filename Specifications} \index[general]{Windows!Considerations for Filename Specifications} -Specifications} Please see the \ilink{Director's Configuration chapter}{win32} of this manual -- 2.39.5