From: Kern Sibbald Date: Mon, 6 Feb 2006 13:51:32 +0000 (+0000) Subject: Update X-Git-Tag: Release-1.38.6~31 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=b1ea333d89152547b8f06a743038b8160bfdfc53;p=bacula%2Fdocs Update --- diff --git a/docs/developers/version.tex b/docs/developers/version.tex index e2f6676b..b0de83ef 100644 --- a/docs/developers/version.tex +++ b/docs/developers/version.tex @@ -1 +1 @@ -1.38.5 (18 January 2006) +1.39.5 (30 January 2006) diff --git a/docs/manual-de/version.tex b/docs/manual-de/version.tex index e2f6676b..b0de83ef 100644 --- a/docs/manual-de/version.tex +++ b/docs/manual-de/version.tex @@ -1 +1 @@ -1.38.5 (18 January 2006) +1.39.5 (30 January 2006) diff --git a/docs/manual/mysql.tex b/docs/manual/mysql.tex index af32170d..669100f7 100644 --- a/docs/manual/mysql.tex +++ b/docs/manual/mysql.tex @@ -41,8 +41,15 @@ the following: \begin{verbatim} mysql-.rpm mysql-server-.rpm +mysql-devel-.rpm \end{verbatim} \normalsize +The names of the packages may vary from distribution to +distribution. It is important to have the devel package loaded as +it contains the libraries and header files necessary to build +Bacula. There may be additional packages that are required to +install the above, for example, zlib and openssl. + Once these packages are installed, you will be able to build Bacula (using the files installed with the mysql package, then run MySQL using the files installed with mysql-server. If you have installed MySQL by rpms, @@ -51,8 +58,9 @@ Bacula, then come back to Phase II of the MySQL installation when indicated to do so. Beginning with Bacula version 1.31, the thread safe version of the -MySQL client library is used, and hence you must add the {\bf -\verb:--:enable-thread-safe-client} option to the {\bf ./configure} as shown below: +MySQL client library is used, and hence you should add the {\bf +\verb:--:enable-thread-safe-client} option to the {\bf +./configure} as shown below: \begin{enumerate} \item Download MySQL source code from @@ -65,9 +73,9 @@ MySQL client library is used, and hence you must add the {\bf Note, the above command requires GNU tar. If you do not have GNU tar, a command such as: -{\bf zcat mysql-filename | tar xvf - +{\bf zcat mysql-filename | tar xvf - } -} will probably accomplish the same thing. +will probably accomplish the same thing. \item cd {\bf mysql-source-directory} diff --git a/docs/manual/security.tex b/docs/manual/security.tex index fdda4903..abe3bde9 100644 --- a/docs/manual/security.tex +++ b/docs/manual/security.tex @@ -98,13 +98,16 @@ subsection*{Configuring and Testing TCP Wrappers} index[general]{Configuring and Testing TCP Wrappers} addcontentsline{toc}{subsection}{Configuring and Testing TCP Wrappers} -TCP Wrappers are implemented if you turn them on when configuring ({\bf -./configure \verb:--:with-libwrap}). With this code enabled, you may control who may -access your daemons. This control is done by modifying the file: {\bf -/etc/hosts.allow}. The program name that {\bf Bacula} uses when applying these -access restrictions is the name you specify in the daemon configuration file. -You must not use the {\bf twist} option in your {\bf /etc/hosts.allow} or it -will terminate the Bacula daemon when a connection is refused. +TCP Wrappers are implemented if you turn them on when configuring +({\bf ./configure \verb:--:with-tcp-wrappers}). +With this code enabled, you may control who may access your +daemons. This control is done by modifying the file: {\bf +/etc/hosts.allow}. The program name that {\bf Bacula} uses when +applying these access restrictions is the name you specify in the +daemon configuration file (see below for examples). +You must not use the {\bf twist} option in your {\bf +/etc/hosts.allow} or it will terminate the Bacula daemon when a +connection is refused. Dan Langille has provided the following information on configuring and testing TCP wrappers with Bacula. @@ -142,7 +145,7 @@ undef-dir : ALL : deny \normalsize You must adjust the daemon names to those found in the respective daemon -configuration files. In these examples, the Director is undef- dir, the +configuration files. In these examples, the Director is undef-dir, the Storage Daemon is undef-sd, and the File Daemon is undef-fd. Adjust to suit your situation. The above example rules assume that the SD, FD, and DIR all reside on the same box. If you have a remote FD client, then the following diff --git a/docs/manual/storedconf.tex b/docs/manual/storedconf.tex index 435d9c40..712a18e0 100644 --- a/docs/manual/storedconf.tex +++ b/docs/manual/storedconf.tex @@ -304,30 +304,73 @@ specified within the Device resource are specific to the Device. The Archive Device directive is required. +\item [Device Type = {\it type-specification}] + \index[sd]{Device Type} + The Device Type specification allows you to explicitly tell Bacula + what kind of device you are defining. It the {\it type-specification} + may be one of the following: + \begin{description} + \item [File] + Tells Bacula that the device is a file. It may either be a + file defined on fixed medium or a removable filesystem such as + USB. All files must be random access devices. + \item [Tape] + The device is a tape device and thus is sequential access. Tape devices + are controlled using ioctl() calls. + \item [Fifo] + The device is a first-in-first out sequential access read-only + or write-only device. + \item [DVD] + The device is a DVD. DVDs are sequential access for writing, but + random access for reading. + \end{description} + + The Device Type directive is not required, and if not specified, Bacula + will attempt to guess what kind of device has been specified using the + Archive Device specification supplied. There are several advantages to + explicitly specifying the Device Type. First, on some systems, block and + character devices have the same type, which means that on those systems, + Bacula is unlikely to be able to correctly guess that a device is a DVD. + Secondly, if you explicitly specify the Device Type, the mount point + need not be defined until the device is opened. This is the case with + most removable devices such as USB that are mounted by the HAL daemon. + If the Device Type is not explicitly specified, then the mount point + must exist when the Storage daemon starts. + + This directive was implemented in Bacula version 1.39.5. + + \item [Media Type = {\it name-string}] \index[sd]{Media Type } - The specified {\bf name-string} names the type of media supported by this - device, for example, "DLT7000". Media type names are arbitrary in that you - set it to anything you want, but must be known to the volume database to keep - track of which storage daemons can read which volumes. The same {\bf - name-string} must appear in the appropriate Storage resource definition in - the Director's configuration file. + The specified {\bf name-string} names the type of media supported by this + device, for example, "DLT7000". Media type names are arbitrary in that you + set them to anything you want, but they must be known to the volume + database to keep track of which storage daemons can read which volumes. In + general, each different storage type should have a unique Media Type + associated with it. The same {\bf name-string} must appear in the + appropriate Storage resource definition in the Director's configuration + file. - Even though the names you assign are arbitrary (i.e. you choose the name you - want), you should take care in specifying them because the Media Type is used - to determine which storage device Bacula will select during restore. Thus you - should probably use the same Media Type specification for all drives where - the Media can be freely interchanged. This is not generally an issue if you - have a single Storage daemon, but it is with multiple Storage daemons, - especially if they have incompatible media. + Even though the names you assign are arbitrary (i.e. you choose the name + you want), you should take care in specifying them because the Media Type + is used to determine which storage device Bacula will select during + restore. Thus you should probably use the same Media Type specification + for all drives where the Media can be freely interchanged. This is not + generally an issue if you have a single Storage daemon, but it is with + multiple Storage daemons, especially if they have incompatible media. - For example, if you specify a Media Type of "DDS-4" then during the - restore, Bacula will be able to choose any Storage Daemon that handles - "DDS-4". If you have an autochanger, you might want to name the Media Type - in a way that is unique to the autochanger, unless you wish to possibly use - the Volumes in other drives. You should also ensure to have unique Media - Type names if the Media is not compatible between drives. This specification - is required for all devices. + For example, if you specify a Media Type of "DDS-4" then during the + restore, Bacula will be able to choose any Storage Daemon that handles + "DDS-4". If you have an autochanger, you might want to name the Media Type + in a way that is unique to the autochanger, unless you wish to possibly use + the Volumes in other drives. You should also ensure to have unique Media + Type names if the Media is not compatible between drives. This + specification is required for all devices. + + In addition, if you are using disk storage, each Device resource will + generally have a different mount point or directory. In order for + Bacula to select the correct Device resource, each one must have a + unique Media Type. \label{Autochanger} \item [Autochanger = {\it Yes|No}] @@ -818,7 +861,9 @@ default, Bacula will only write one end of file to terminate the tape. \addcontentsline{toc}{subsection}{Devices that require a mount (DVD)} All the directives in this section are implemented only in -Bacula version 1.37 and later. +Bacula version 1.37 and later. As of version 1.39.5, the directives +"Requires Mount", "Mount Point", "Mount Command", and "Unmount Command" +apply to removable filesystems such as USB in addition to DVD. \begin{description} diff --git a/docs/manual/version.tex b/docs/manual/version.tex index e2f6676b..b0de83ef 100644 --- a/docs/manual/version.tex +++ b/docs/manual/version.tex @@ -1 +1 @@ -1.38.5 (18 January 2006) +1.39.5 (30 January 2006)