From: Kern Sibbald Date: Fri, 13 Oct 2006 15:43:58 +0000 (+0000) Subject: Fix errors in the manual that truncated the pdf X-Git-Tag: Release-2.0.0~363 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=c49ced428ad9fe7677a0bfbb6215882d6d8e956a;p=bacula%2Fdocs Fix errors in the manual that truncated the pdf --- diff --git a/docs/developers/version.tex b/docs/developers/version.tex index e7b01c69..24522f04 100644 --- a/docs/developers/version.tex +++ b/docs/developers/version.tex @@ -1 +1 @@ -1.39.23 (28 September 2006) +1.39.26 (14 October 2006) diff --git a/docs/home-page/pages/professional.php b/docs/home-page/pages/professional.php index ce299eec..71258d1e 100644 --- a/docs/home-page/pages/professional.php +++ b/docs/home-page/pages/professional.php @@ -75,6 +75,34 @@ http://www.axiomnetworking.ca
+ + +
+ + + + Bayer Technology Group + + + + Jonathan B Bayer
+ Bayer Technology Group, 23 Exeter Rd., East Windsor, NJ 08520 USA
+ +1 (609) 632-1200
+ +1 (609) 658-9408 (mobile)
+
+ Our focus is on assisting and providing high + quality IT services to individuals, small businesses and + organizations with computer and information technology needs, + but who often don't need or have a budget for a full time IT + staff. We specialize in Desktop systems, Local Area Network + (LAN), Internet, Computer Systems Security and Disaster + Recovery Planning and Implementation using Microsoft and + Linux based solutions.

http://www.BayerTechnologyGroup.com
+ + + +
@@ -93,6 +121,7 @@ http://www.langille.org/ +
diff --git a/docs/manual-de/version.tex b/docs/manual-de/version.tex index e7b01c69..24522f04 100644 --- a/docs/manual-de/version.tex +++ b/docs/manual-de/version.tex @@ -1 +1 @@ -1.39.23 (28 September 2006) +1.39.26 (14 October 2006) diff --git a/docs/manual/catmaintenance.tex b/docs/manual/catmaintenance.tex index 87f86daf..4ef7b61d 100644 --- a/docs/manual/catmaintenance.tex +++ b/docs/manual/catmaintenance.tex @@ -177,6 +177,12 @@ running dbcheck before (or possibly after) using the MySQL database repair program. It can clean up many of the orphaned record problems, and certain other inconsistencies in the Bacula database. +\subsection*{MySQL Table is Full} +\index[general]{Database!MySQL Table is Full} +\index[general]{MySQL Table is Full} +\addcontentsline{toc}{subsection}{MySQL Table is Full} + + If you are running into the error {\bf The table 'File' is full ...}, it is probably because on version 4.x MySQL, the table is limited by default to a maximum size of 4 GB and you have probably run into @@ -193,7 +199,7 @@ SHOW TABLE STATUS FROM bacula like "File"; \end{verbatim} \normalsize -If the column labeld "Max_data_length" is around 4Gb, this is likely +If the column labeld "Max\_data\_length" is around 4Gb, this is likely to be the source of your problem, and you can modify it with: \footnotesize @@ -219,6 +225,19 @@ The row and pointer size changes should already be the default on MySQL version 5.x, so making these changes should only be necessary on MySQL 4.x depending on the size of your catalog database. +\subsection*{MySQL Server Has Gone Away} +\index[general]{Database!MySQL Server Has Gone Away} +\index[general]{MySQL Server Has Gone Away} +\addcontentsline{toc}{subsection}{MySQL Server Has Gone Away} +If you are having problems with the MySQL server disconnecting or with +messages saying that your MySQL server has gone away, then please read +the MySQL documentation, which can be found at: + +\elink{http://dev.mysql.com/doc/refman/5.0/en/gone-away.html} +{http://dev.mysql.com/doc/refman/5.0/en/gone-away.html} + + + \label{RepairingPSQL} \subsection*{Repairing Your PostgreSQL Database} @@ -348,9 +367,9 @@ show index from Path; \normalsize and what is important is that for Filename, you have an index with -Key_name "Name" and Sub_part "255". For Pth, you should have a Key_name -"Path" and Sub_part "255". If one or the other does not exist or the -Sub_part is less that 255, you can drop and recreate the appropriate +Key\_name "Name" and Sub\_part "255". For Pth, you should have a Key\_name +"Path" and Sub\_part "255". If one or the other does not exist or the +Sub\_part is less that 255, you can drop and recreate the appropriate index with: \footnotesize diff --git a/docs/manual/console.tex b/docs/manual/console.tex index 60c98119..8a405072 100644 --- a/docs/manual/console.tex +++ b/docs/manual/console.tex @@ -163,6 +163,9 @@ order ... \item [all] Permitted on the status and show commands to specify all components or resources respectively. +\item [allfrompool] + Permitted on the update command to specify that all Volumes in the + pool (specified on the command line) should be updated. \item [before] Used in the restore command. \item [bootstrap] diff --git a/docs/manual/consoleconf.tex b/docs/manual/consoleconf.tex index c45b5a47..baf97d3e 100644 --- a/docs/manual/consoleconf.tex +++ b/docs/manual/consoleconf.tex @@ -269,6 +269,8 @@ and do with Bacula. The following is an example of a bconsole conf file that can access several Directors and has different Consoles depending on the director: +\footnotesize +\begin{verbatim} Director { Name = MyDirector DIRport = 9101 diff --git a/docs/manual/dvd.tex b/docs/manual/dvd.tex index e93a5d5f..c2a72060 100644 --- a/docs/manual/dvd.tex +++ b/docs/manual/dvd.tex @@ -27,7 +27,7 @@ NOT} work with Bacula. You must apply a patch which can be found in the {\bf patches} directory of Bacula sources with the name {\bf dvd+rw-tools-5.21.4.10.8.bacula.patch} for version 5.21 of the tools, or patch {bf dvd+rw-tools-6.1.bacula.patch} if you have version 6.1 -on your system. Unfortunately, this requires you to build the dvd_rw-tools +on your system. Unfortunately, this requires you to build the dvd\_rw-tools from source. The fact that Bacula cannot use the OS to write directly diff --git a/docs/manual/fileset.tex b/docs/manual/fileset.tex index c3b1c171..a243a7a4 100644 --- a/docs/manual/fileset.tex +++ b/docs/manual/fileset.tex @@ -494,7 +494,7 @@ Change: 2005-11-06 12:36:48.000000000 +0100 \item [noatime=yes|no] \index[dir]{noatime} \index[dir]{Directive!noatime} - If enabled, and if your Operating System supports the O_NOATIME file + If enabled, and if your Operating System supports the O\_NOATIME file open flag, Bacula will open all files to be backed up with this option. It makes it possible to read a file without updating the inode atime (and also without the inode ctime update which happens if you try to set diff --git a/docs/manual/general.tex b/docs/manual/general.tex index 5d845e0d..3cbff64f 100644 --- a/docs/manual/general.tex +++ b/docs/manual/general.tex @@ -108,7 +108,7 @@ Bacula is made up of the following five major components or services: physical backup media or volumes. In other words, the Storage daemon is responsible for reading and writing your tapes (or other storage media, e.g. files). For more details see the Storage Services Daemon Design - Document in the Bacula Developer's Guild. The Storage services runs as + Document in the Bacula Developer's Guide. The Storage services runs as a daemon on the machine that has the backup device (usually a tape drive). \item diff --git a/docs/manual/install.tex b/docs/manual/install.tex index bead1456..87b636df 100644 --- a/docs/manual/install.tex +++ b/docs/manual/install.tex @@ -3,12 +3,12 @@ \section*{Installing Bacula} \label{_ChapterStart17} -\index[general]{Bacula!Installing } -\index[general]{Installing Bacula } +\index[general]{Bacula!Installing} +\index[general]{Installing Bacula} \addcontentsline{toc}{section}{Installing Bacula} \subsection*{General} -\index[general]{General } +\index[general]{General} \addcontentsline{toc}{subsection}{General} In general, you will need the Bacula source release, and if you want to run @@ -67,8 +67,8 @@ the Bacula CVS. The released files are: \label{upgrading1} \subsection*{Upgrading Bacula} -\index[general]{Bacula!Upgrading } -\index[general]{Upgrading Bacula } +\index[general]{Bacula!Upgrading} +\index[general]{Upgrading Bacula} \addcontentsline{toc}{subsection}{Upgrading Bacula} If you are upgrading from one Bacula version to another, you should first @@ -211,8 +211,8 @@ the new code. Beta releases are made with the following considerations: \end{itemize} -\subsection*{Dependency Packages} \label{Dependency} +\subsection*{Dependency Packages} \index[general]{Dependency Packages} \index[general]{Packages!Dependency} \addcontentsline{toc}{subsection}{Dependency Packages} @@ -245,13 +245,11 @@ to time, the current makeup is the following: \addcontentsline{lot}{table}{Dependency Packages} \begin{longtable}{|l|l|} \hline -\multicolumn{1}{|c| }{\bf 3rd Party Package } & \multicolumn{1}{c| }{\bf -depkgs } & \multicolumn{1} \\ - \hline {SQLite } & \multicolumn{1}{c| }{X } & \multicolumn{1} \\ - \hline {SQLite3 } & \multicolumn{1}{c| }{X } & \multicolumn{1} \\ - \hline {mtx } & \multicolumn{1}{c| }{X } & \multicolumn{1} \\ +\multicolumn{1}{|c| }{\bf 3rd Party Package} & \multicolumn{1}{c| }{\bf depkgs} \\ + \hline {SQLite } & \multicolumn{1}{c| }{X } \\ + \hline {SQLite3 } & \multicolumn{1}{c| }{X } \\ + \hline {mtx } & \multicolumn{1}{c| }{X } \\ \hline - \end{longtable} Note, some of these packages are quite large, so that building them can be a @@ -292,8 +290,8 @@ src/win32/README.mingw32 for more details. \subsection*{Supported Operating Systems} \label{Systems} -\index[general]{Systems!Supported Operating } -\index[general]{Supported Operating Systems } +\index[general]{Systems!Supported Operating} +\index[general]{Supported Operating Systems} \addcontentsline{toc}{subsection}{Supported Operating Systems} Please see the @@ -302,8 +300,8 @@ of the QuickStart chapter of this manual. \subsection*{Building Bacula from Source} \label{Building} -\index[general]{Source!Building Bacula from } -\index[general]{Building Bacula from Source } +\index[general]{Source!Building Bacula from} +\index[general]{Building Bacula from Source} \addcontentsline{toc}{subsection}{Building Bacula from Source} The basic installation is rather simple. @@ -551,8 +549,8 @@ support it. \subsection*{What Database to Use?} \label{DB} -\index[general]{What Database to Use? } -\index[general]{Use!What Database to } +\index[general]{What Database to Use?} +\index[general]{Use!What Database to} \addcontentsline{toc}{subsection}{What Database to Use?} Before building Bacula you need to decide if you want to use SQLite, MySQL, or @@ -587,8 +585,8 @@ If you wish to use SQLite as the Bacula catalog, please see this manual. \subsection*{Quick Start} -\index[general]{Quick Start } -\index[general]{Start!Quick } +\index[general]{Quick Start} +\index[general]{Start!Quick} \addcontentsline{toc}{subsection}{Quick Start} There are a number of options and important considerations given below @@ -612,8 +610,8 @@ come back to this chapter and read the details presented below. \subsection*{Configure Options} \label{Options} -\index[general]{Options!Configure } -\index[general]{Configure Options } +\index[general]{Options!Configure} +\index[general]{Configure Options} \addcontentsline{toc}{subsection}{Configure Options} The following command line options are available for {\bf configure} to @@ -621,12 +619,12 @@ customize your installation. \begin{description} \item [ {-}{-}sysbindir=\lt{}binary-path\gt{}] - \index[general]{{-}{-}sysbindir } + \index[general]{{-}{-}sysbindir} Defines where the Bacula binary (executable) files will be placed during a {\bf make install} command. \item [ {-}{-}sysconfdir=\lt{}config-path\gt{}] - \index[general]{{-}{-}sysconfdir } + \index[general]{{-}{-}sysconfdir} Defines where the Bacula configuration files should be placed during a {\bf make install} command. @@ -657,7 +655,7 @@ customize your installation. \item [ {-}{-}enable-smartalloc ] - \index[general]{{-}{-}enable-smartalloc } + \index[general]{{-}{-}enable-smartalloc} This enables the inclusion of the Smartalloc orphaned buffer detection code. This option is highly recommended. Because we never build without this option, you may experience problems if it is not enabled. @@ -666,14 +664,14 @@ customize your installation. configuration parameter is used while building Bacula \item [ {-}{-}enable-gnome ] - \index[general]{{-}{-}enable-gnome } + \index[general]{{-}{-}enable-gnome} If you have GNOME installed on your computer including the gnome development libraries, and you want to use the GNOME GUI Console interface to Bacula, you must specify this option. Doing so will build everything in the {\bf src/gnome-console} directory. \item [ {-}{-}enable-wx-console ] - \index[general]{{-}{-}enable-wx-console } + \index[general]{{-}{-}enable-wx-console} If you have wxWidgets installed on your computer and you want to use the wxWidgets GUI Console interface to Bacula, you must specify this option. Doing so will build everything in the {\bf src/wx-console} directory. @@ -683,7 +681,7 @@ customize your installation. \item [ {-}{-}enable-tray-monitor ] - \index[general]{{-}{-}enable-tray-monitor } + \index[general]{{-}{-}enable-tray-monitor} If you have GTK installed on your computer, you run a graphical environment or a window manager compatible with the FreeDesktop system tray standard (like KDE and GNOME) and you want to use a GUI to monitor @@ -691,7 +689,7 @@ customize your installation. everything in the {\bf src/tray-monitor} directory. \item [ {-}{-}enable-static-tools] - \index[general]{{-}{-}enable-static-tools } + \index[general]{{-}{-}enable-static-tools} This option causes the linker to link the Storage daemon utility tools ({\bf bls}, {\bf bextract}, and {\bf bscan}) statically. This permits using them without having the shared libraries loaded. If you have @@ -701,7 +699,7 @@ customize your installation. \item [ {-}{-}enable-static-fd] - \index[general]{{-}{-}enable-static-fd } + \index[general]{{-}{-}enable-static-fd} This option causes the make process to build a {\bf static-bacula-fd} in addition to the standard File daemon. This static version will include statically linked libraries and is required for the Bare Metal recovery. @@ -723,7 +721,7 @@ customize your installation. \item [ {-}{-}enable-static-sd] - \index[general]{{-}{-}enable-static-sd } + \index[general]{{-}{-}enable-static-sd} This option causes the make process to build a {\bf static-bacula-sd} in addition to the standard Storage daemon. This static version will include statically linked libraries and could be useful during a Bare @@ -742,7 +740,7 @@ customize your installation. \item [ {-}{-}enable-static-dir] - \index[general]{{-}{-}enable-static-dir } + \index[general]{{-}{-}enable-static-dir} This option causes the make process to build a {\bf static-bacula-dir} in addition to the standard Director. This static version will include statically linked libraries and could be useful during a Bare Metal @@ -760,7 +758,7 @@ customize your installation. \item [ {-}{-}enable-static-cons] - \index[general]{{-}{-}enable-static-cons } + \index[general]{{-}{-}enable-static-cons} This option causes the make process to build a {\bf static-console} and a {\bf static-gnome-console} in addition to the standard console. This static version will include statically linked libraries and could be @@ -778,7 +776,7 @@ customize your installation. \item [ {-}{-}enable-client-only] - \index[general]{{-}{-}enable-client-only } + \index[general]{{-}{-}enable-client-only} This option causes the make process to build only the File daemon and the libraries that it needs. None of the other daemons, storage tools, nor the console will be built. Likewise a {\bf make install} will then @@ -797,14 +795,14 @@ customize your installation. need to load additional static libraries. \item [ {-}{-}enable-build-dird] - \index[general]{{-}{-}enable-build-dird } + \index[general]{{-}{-}enable-build-dird} This option causes the make process to build the Director and the Director's tools. By default, this option is on, but you may turn it off by using {\bf {-}{-}disable-build-dird} to prevent the Director from being built. \item [ {-}{-}enable-build-stored] - \index[general]{{-}{-}enable-build-stored } + \index[general]{{-}{-}enable-build-stored} This option causes the make process to build the Storage daemon. By default, this option is on, but you may turn it off by using {\bf {-}{-}disable-build-stored} to prevent the @@ -812,7 +810,7 @@ customize your installation. \item [ {-}{-}enable-largefile] - \index[general]{{-}{-}enable-largefile } + \index[general]{{-}{-}enable-largefile} This option (default) causes Bacula to be built with 64 bit file address support if it is available on your system. This permits Bacula to read and write files greater than 2 GBytes in size. You may disable this feature and @@ -827,7 +825,7 @@ customize your installation. In such a case, Bacula will revert to using English. \item [ {-}{-}with-sqlite=\lt{}sqlite-path\gt{}] - \index[general]{{-}{-}with-sqlite } + \index[general]{{-}{-}with-sqlite} This enables use of the SQLite version 2.8.x database. The {\bf sqlite-path} is not normally specified as Bacula looks for the necessary components in a standard location ({\bf depkgs/sqlite}). See @@ -837,7 +835,7 @@ customize your installation. See the note below under the {-}{-}with-postgresql item. \item [ {-}{-}with-sqlite3=\lt{}sqlite3-path\gt{}] - \index[general]{{-}{-}with-sqlite3 } + \index[general]{{-}{-}with-sqlite3} This enables use of the SQLite version 3.x database. The {\bf sqlite3-path} is not normally specified as Bacula looks for the necessary components in a standard location ({\bf depkgs/sqlite3}). See @@ -845,7 +843,7 @@ customize your installation. this manual for more details. \item [ {-}{-}with-mysql=\lt{}mysql-path\gt{}] - \index[general]{{-}{-}with-mysql } + \index[general]{{-}{-}with-mysql} This enables building of the Catalog services for Bacula. It assumes that MySQL is running on your system, and expects it to be installed in the {\bf mysql-path} that you specify. Normally, if MySQL is installed @@ -857,7 +855,7 @@ customize your installation. See the note below under the {-}{-}with-postgresql item. \item [ {-}{-}with-postgresql=\lt{}path\gt{}] - \index[general]{{-}{-}with-postgresql } + \index[general]{{-}{-}with-postgresql} This provides an explicit path to the PostgreSQL libraries if Bacula cannot find it by default. Normally to build with PostgreSQL, you would simply use {\bf {-}{-}with-postgresql}. @@ -885,7 +883,7 @@ customize your installation. \item [ {-}{-}with-python=\lt{}path\gt{}] - \index[general]{{-}{-}with-python } + \index[general]{{-}{-}with-python} This option enables Bacula support for Python. If no path is supplied, configure will search the standard library locations for Python 2.2, 2.3, or 2.4. If it cannot @@ -901,14 +899,14 @@ customize your installation. Language Support (NLS). \item [ {-}{-}enable-conio] - \index[general]{{-}{-}enable-conio } + \index[general]{{-}{-}enable-conio} Tells Bacula to enable building the small, light weight readline replacement routine. It is generally much easier to configure than readline, although, like readline, it needs either the termcap or ncurses library. \item [ {-}{-}with-readline=\lt{}readline-path\gt{}] - \index[general]{{-}{-}with-readline } + \index[general]{{-}{-}with-readline} Tells Bacula where {\bf readline} is installed. Normally, Bacula will find readline if it is in a standard library. If it is not found and no {-}{-}with-readline is specified, readline will be disabled. This @@ -917,13 +915,13 @@ customize your installation. supported, so you are on your own if you have problems. \item [ {-}{-}enable-readline] - \index[general]{{-}{-}enable-readline } + \index[general]{{-}{-}enable-readline} Tells Bacula to enable readline support. It is normally disabled due to the large number of configuration problems and the fact that the package seems to change in incompatible ways from version to version. \item [ {-}{-}with-tcp-wrappers=\lt{}path\gt{}] - \index[general]{{-}{-}with-tcp-wrappers } + \index[general]{{-}{-}with-tcp-wrappers} \index[general]{TCP Wrappers} \index[general]{Wrappers!TCP} \index[general]{libwrappers} @@ -946,7 +944,7 @@ customize your installation. tcp\_wrappers. \item [ {-}{-}with-working-dir=\lt{}working-directory-path\gt{} ] - \index[general]{{-}{-}with-working-dir } + \index[general]{{-}{-}with-working-dir} This option is mandatory and specifies a directory into which Bacula may safely place files that will remain between Bacula executions. For example, if the internal database is used, Bacula will keep those files in this @@ -956,7 +954,7 @@ customize your installation. you must ensure that it exists before using Bacula for the first time. \item [ {-}{-}with-base-port=\lt{}port=number\gt{}] - \index[general]{{-}{-}with-base-port } + \index[general]{{-}{-}with-base-port} In order to run, Bacula needs three TCP/IP ports (one for the Bacula Console, one for the Storage daemon, and one for the File daemon). The {\bf \verb:--:with-baseport} option will automatically assign three ports beginning at @@ -969,19 +967,19 @@ customize your installation. may also accomplish the same thing by directly editing them later. \item [ {-}{-}with-dump-email=\lt{}email-address\gt{}] - \index[general]{{-}{-}with-dump-email } + \index[general]{{-}{-}with-dump-email} This option specifies the email address where any core dumps should be set. This option is normally only used by developers. \item [ {-}{-}with-pid-dir=\lt{}PATH\gt{} ] - \index[general]{{-}{-}with-pid-dir } + \index[general]{{-}{-}with-pid-dir} This specifies where Bacula should place the process id file during execution. The default is: {\bf /var/run}. This directory is not created by the install process, so you must ensure that it exists before using Bacula the first time. \item [ {-}{-}with-subsys-dir=\lt{}PATH\gt{}] - \index[general]{{-}{-}with-subsys-dir } + \index[general]{{-}{-}with-subsys-dir} This specifies where Bacula should place the subsystem lock file during execution. The default is {\bf /var/run/subsys}. Please make sure that you do not specify the same directory for this directory and for the {\bf sbindir} @@ -990,25 +988,25 @@ customize your installation. create it before using Bacula. \item [ {-}{-}with-dir-password=\lt{}Password\gt{}] - \index[general]{{-}{-}with-dir-password } + \index[general]{{-}{-}with-dir-password} This option allows you to specify the password used to access the Directory (normally from the Console program). If it is not specified, configure will automatically create a random password. \item [ {-}{-}with-fd-password=\lt{}Password\gt{} ] - \index[general]{{-}{-}with-fd-password } + \index[general]{{-}{-}with-fd-password} This option allows you to specify the password used to access the File daemon (normally called from the Director). If it is not specified, configure will automatically create a random password. \item [ {-}{-}with-sd-password=\lt{}Password\gt{} ] - \index[general]{{-}{-}with-sd-password } + \index[general]{{-}{-}with-sd-password} This option allows you to specify the password used to access the Directory (normally called from the Director). If it is not specified, configure will automatically create a random password. \item [ {-}{-}with-dir-user=\lt{}User\gt{} ] - \index[general]{{-}{-}with-dir-user } + \index[general]{{-}{-}with-dir-user} This option allows you to specify the Userid used to run the Director. The Director must be started as root, but doesn't need to run as root, and after doing preliminary initializations, it can "drop" to the UserId @@ -1019,7 +1017,7 @@ customize your installation. \item [ {-}{-}with-dir-group=\lt{}Group\gt{} ] - \index[general]{{-}{-}with-dir-group } + \index[general]{{-}{-}with-dir-group} This option allows you to specify the GroupId used to run the Director. The Director must be started as root, but doesn't need to run as root, and after doing preliminary initializations, it can "drop" to the GroupId specified @@ -1029,7 +1027,7 @@ customize your installation. working directory group will be set to {\bf Group}. \item [ {-}{-}with-sd-user=\lt{}User\gt{} ] - \index[general]{{-}{-}with-sd-user } + \index[general]{{-}{-}with-sd-user} This option allows you to specify the Userid used to run the Storage daemon. The Storage daemon must be started as root, but doesn't need to run as root, and after doing preliminary initializations, it can "drop" to the UserId @@ -1038,14 +1036,14 @@ customize your installation. it needs. \item [ {-}{-}with-sd-group=\lt{}Group\gt{} ] - \index[general]{{-}{-}with-sd-group } + \index[general]{{-}{-}with-sd-group} This option allows you to specify the GroupId used to run the Storage daemon. The Storage daemon must be started as root, but doesn't need to run as root, and after doing preliminary initializations, it can "drop" to the GroupId specified on this option. \item [ {-}{-}with-fd-user=\lt{}User\gt{} ] - \index[general]{{-}{-}with-fd-user } + \index[general]{{-}{-}with-fd-user} This option allows you to specify the Userid used to run the File daemon. The File daemon must be started as root, and in most cases, it needs to run as root, so this option is used only in very special cases, after doing @@ -1053,7 +1051,7 @@ customize your installation. option. \item [ {-}{-}with-fd-group=\lt{}Group\gt{} ] - \index[general]{{-}{-}with-fd-group } + \index[general]{{-}{-}with-fd-group} This option allows you to specify the GroupId used to run the File daemon. The File daemon must be started as root, and in most cases, it must be run as root, however, after doing preliminary initializations, it can "drop" to @@ -1065,8 +1063,8 @@ Note, many other options are presented when you do a {\bf ./configure \verb:--:help}, but they are not implemented. \subsection*{Recommended Options for most Systems} -\index[general]{Systems!Recommended Options for most } -\index[general]{Recommended Options for most Systems } +\index[general]{Systems!Recommended Options for most} +\index[general]{Recommended Options for most Systems} \addcontentsline{toc}{subsection}{Recommended Options for most Systems} For most systems, we recommend starting with the following options: @@ -1095,7 +1093,7 @@ running Bacula for the first time. See below for an example of how Kern does it. \subsection*{RedHat} -\index[general]{RedHat } +\index[general]{RedHat} \addcontentsline{toc}{subsection}{RedHat} Using SQLite: @@ -1163,7 +1161,7 @@ in the Storage daemon first. The solution is to compile Bacula ensuring that no optimization is turned on (normally it is -O2). \subsection*{Solaris} -\index[general]{Solaris } +\index[general]{Solaris} \addcontentsline{toc}{subsection}{Solaris} To build Bacula from source, you will need the following installed on your @@ -1217,7 +1215,7 @@ PATH=/usr/bin::/usr/ccs/bin:/etc:/usr/openwin/bin:/usr/local/bin:/usr/sfw/bin:/o \normalsize \subsection*{FreeBSD} -\index[general]{FreeBSD } +\index[general]{FreeBSD} \addcontentsline{toc}{subsection}{FreeBSD} Please see: @@ -1235,15 +1233,15 @@ with FreeBSD native threads rather than LinuxTreads. Mixing the two will probably not work. \subsection*{Win32} -\index[general]{Win32 } +\index[general]{Win32} \addcontentsline{toc}{subsection}{Win32} To install the binary Win32 version of the File daemon please see the \ilink{Win32 Installation Chapter}{_ChapterStart7} in this document. \subsection*{Kern's Configure Script} -\index[general]{Script!Kern's Configure } -\index[general]{Kern's Configure Script } +\index[general]{Script!Kern's Configure} +\index[general]{Kern's Configure Script} \addcontentsline{toc}{subsection}{Kern's Configure Script} The script that I use for building on my "production" Linux machines is: @@ -1285,8 +1283,8 @@ bacula-sd 9103/tcp \normalsize \subsection*{Installing Bacula} -\index[general]{Bacula!Installing } -\index[general]{Installing Bacula } +\index[general]{Bacula!Installing} +\index[general]{Installing Bacula} \addcontentsline{toc}{subsection}{Installing Bacula} Before setting up your configuration files, you will want to install Bacula in @@ -1305,8 +1303,8 @@ previously installed and run Bacula you will want to discard or ignore the configuration files with the appended {\bf .new}. \subsection*{Building a File Daemon or Client} -\index[general]{Client!Building a File Daemon or } -\index[general]{Building a File Daemon or Client } +\index[general]{Client!Building a File Daemon or} +\index[general]{Building a File Daemon or Client} \addcontentsline{toc}{subsection}{Building a File Daemon or Client} If you run the Director and the Storage daemon on one machine and you wish to @@ -1333,8 +1331,8 @@ client will be built. \label{autostart} \subsection*{Auto Starting the Daemons} -\index[general]{Daemons!Auto Starting the } -\index[general]{Auto Starting the Daemons } +\index[general]{Daemons!Auto Starting the} +\index[general]{Auto Starting the Daemons} \addcontentsline{toc}{subsection}{Auto Starting the Daemons} If you wish the daemons to be automatically started and stopped when your @@ -1369,8 +1367,8 @@ make install-autostart-fd \normalsize \subsection*{Other Make Notes} -\index[general]{Notes!Other Make } -\index[general]{Other Make Notes } +\index[general]{Notes!Other Make} +\index[general]{Other Make Notes} \addcontentsline{toc}{subsection}{Other Make Notes} To simply build a new executable in any directory, enter: @@ -1484,8 +1482,8 @@ wx-console.conf \label{monitor} \subsection*{Installing Tray Monitor} -\index[general]{Monitor!Installing Tray } -\index[general]{Installing Tray Monitor } +\index[general]{Monitor!Installing Tray} +\index[general]{Installing Tray Monitor} \addcontentsline{toc}{subsection}{Installing Tray Monitor} The Tray Monitor is already installed if you used the {\bf @@ -1503,7 +1501,7 @@ If it doesn't, follow the instructions below related to your environment or window manager. \subsubsection*{GNOME} -\index[general]{GNOME } +\index[general]{GNOME} \addcontentsline{toc}{subsubsection}{GNOME} System tray, or notification area if you use the GNOME terminology, has been @@ -1512,7 +1510,7 @@ your panels, open the menu {\bf Add to this Panel}, then {\bf Utility} and finally click on {\bf Notification Area}. \subsubsection*{KDE} -\index[general]{KDE } +\index[general]{KDE} \addcontentsline{toc}{subsubsection}{KDE} System tray has been supported in KDE since version 3.1. To activate it, @@ -1520,16 +1518,16 @@ right-click on one of your panels, open the menu {\bf Add}, then {\bf Applet} and finally click on {\bf System Tray}. \subsubsection*{Other window managers} -\index[general]{Managers!Other window } -\index[general]{Other window managers } +\index[general]{Managers!Other window} +\index[general]{Other window managers} \addcontentsline{toc}{subsubsection}{Other window managers} Read the documentation to know if the Freedesktop system tray standard is supported by your window manager, and if applicable, how to activate it. \subsection*{Modifying the Bacula Configuration Files} -\index[general]{Modifying the Bacula Configuration Files } -\index[general]{Files!Modifying the Bacula Configuration } +\index[general]{Modifying the Bacula Configuration Files} +\index[general]{Files!Modifying the Bacula Configuration} \addcontentsline{toc}{subsection}{Modifying the Bacula Configuration Files} See the chapter diff --git a/docs/manual/restore.tex b/docs/manual/restore.tex index 4085e774..1f5ff084 100644 --- a/docs/manual/restore.tex +++ b/docs/manual/restore.tex @@ -1019,7 +1019,7 @@ OK to run? (yes/mod/no): XXX Database sections). Also, please note that after you restore your database from an ASCII - backup, you do NOT want to do a {\bf make_bacula_tables} command, or + backup, you do NOT want to do a {\bf make\_bacula\_tables} command, or you will probably erase your newly restored database tables. @@ -1112,7 +1112,7 @@ FileIndex=1-1 XXX Database sections). Also, please note that after you restore your database from an ASCII - backup, you do NOT want to do a {\bf make_bacula_tables} command, or + backup, you do NOT want to do a {\bf make\_bacula\_tables} command, or you will probably erase your newly restored database tables. \item [Solution withou a Job Listing] diff --git a/docs/manual/rpm-faq.tex b/docs/manual/rpm-faq.tex index 8b75ead3..b5aa3087 100644 --- a/docs/manual/rpm-faq.tex +++ b/docs/manual/rpm-faq.tex @@ -197,7 +197,7 @@ creation of debug rpm packages is: \label{faq7} {\bf Is there an easier way than sorting out all these command line options?} Yes, there is a gui wizard shell script which you can use to rebuild the src rpm package. - Look in the source archive for platforms/contrib-rpm/rpm_wizard.sh. This script will + Look in the source archive for platforms/contrib-rpm/rpm\_wizard.sh. This script will allow you to specify build options using gnome dialog screens. It requires zenity. \item @@ -207,8 +207,8 @@ creation of debug rpm packages is: \footnotesize \begin{verbatim} chown bacula.bacula /var/bacula/* - chown root.bacula /var/bacula/bacula-fd.9102.state - chown bacula.disk /var/bacula/bacula-sd.9103.state + chown root.bacula /var/bacula/bacula-fd.9102.state + chown bacula.disk /var/bacula/bacula-sd.9103.state \end{verbatim} \normalsize @@ -355,4 +355,3 @@ can occur: more information on devices. \end{itemize} - diff --git a/docs/manual/version.tex b/docs/manual/version.tex index 883b54e2..24522f04 100644 --- a/docs/manual/version.tex +++ b/docs/manual/version.tex @@ -1 +1 @@ -1.39.25 (08 October 2006) +1.39.26 (14 October 2006) diff --git a/docs/manual/win32.tex b/docs/manual/win32.tex index 36eed103..5358b632 100644 --- a/docs/manual/win32.tex +++ b/docs/manual/win32.tex @@ -362,7 +362,7 @@ Marc Brueckner for doing the tests: \hline {WinMe} & {WinNT} & {Works (SYSTEM permissions) } \\ \hline {WinMe} & {WinXP} & {Works (SYSTEM permissions) } \\ \hline {WinMe} & {Linux} & {Works (SYSTEM permissions) } \\ - \hline {\} & {\} & {\ } \\ + \hline {\ } & {\ } & {\ } \\ \hline {WinXP} & {WinXP} & {Works } \\ \hline {WinXP} & {WinNT} & {Works (all files OK, but got "The data is invalid" message) } \\ @@ -370,14 +370,14 @@ message) } \\ \hline {WinXP} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.} \\ \hline {WinXP} & {Linux} & {Error: Win32 data stream not supported. } \\ \hline {WinXP} & {Linux} & {Works if {\bf Portable=yes} specified during backup.}\\ - \hline {\} & {\} & {\ } \\ + \hline {\ } & {\ } & {\ } \\ \hline {WinNT} & {WinNT} & {Works } \\ \hline {WinNT} & {WinXP} & {Works } \\ \hline {WinNT} & {WinMe} & {Error: Win32 data stream not supported. } \\ \hline {WinNT} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.}\\ \hline {WinNT} & {Linux} & {Error: Win32 data stream not supported. } \\ \hline {WinNT} & {Linux} & {Works if {\bf Portable=yes} specified during backup. }\\ - \hline {\} & {\} & {\ } \\ + \hline {\ } & {\ } & {\ } \\ \hline {Linux} & {Linux} & {Works } \\ \hline {Linux} & {WinNT} & {Works (SYSTEM permissions) } \\ \hline {Linux} & {WinMe} & {Works } \\