\item
\label{faq1}
{\bf How do I build Bacula for platform xxx?}
- The bacula spec file contains defines to build for several platforms:
- Red Hat 7.x (rh7), Red Hat 8.0 (rh8), Red Hat 9 (rh9), Fedora Core (fc1,
- fc3, fc4, fc5, fc6, fc7, fc8), Whitebox Enterprise Linux 3.0 (wb3), Red Hat Enterprise Linux
- (rhel3, rhel4, rhel5), Mandrake 10.x (mdk), Mandriva 2006.x (mdv) CentOS (centos3, centos4, centos5)
- Scientific Linux (sl3, sl4, sl5) and SuSE (su9, su10, su102, su103, su110). The package build is controlled by a mandatory define set at the beginning of the file. These defines basically just control the dependency information that gets coded into the finished rpm package as well
+ The bacula spec file contains defines to build for several platforms: \\
+ \\
+ Red Hat 7.x (rh7), Red Hat 8.0 (rh8), Red Hat 9 (rh9), \\
+ Fedora Core (fc1, fc3, fc4, fc5, fc6, fc7, fc8), \\
+ Whitebox Enterprise Linux 3.0 (wb3), \\
+ Red Hat Enterprise Linux (rhel3, rhel4, rhel5), \\
+ Mandrake 10.x (mdk), Mandriva 2006.x (mdv), \\
+ CentOS (centos3, centos4, centos5) \\
+ Scientific Linux (sl3, sl4, sl5) and \\
+ SuSE (su9, su10, su102, su103, su110). \\
+ \\
+ The package build is controlled by a mandatory define set at the beginning of the file. These defines basically just control the dependency information that gets coded into the finished rpm package as well
as any special configure options required. The platform define may be edited
in the spec file directly (by default all defines are set to 0 or "not set").
For example, to build the Red Hat 7.x package find the line in the spec file
\item
\label{faq3}
- {\bf What other defines are used?}
+ {\bf What other defines are used?} \\
Three other building defines of note are the depkgs\_version, docs\_version and
\_rescuever identifiers. These two defines are set with each release and must
match the version of those sources that are being used to build the packages.
\item
\label{faq4}
{\bf I'm getting errors about not having permission when I try to build the
- packages. Do I need to be root?}
+ packages. Do I need to be root?} \\
No, you do not need to be root and, in fact, it is better practice to
build rpm packages as a non-root user. Bacula packages are designed to
be built by a regular user but you must make a few changes on your
\item
\label{faq5}
{\bf I'm building my own rpms but on all platforms and compiles I get an
- unresolved dependency for something called /usr/afsws/bin/pagsh.} This
- is a shell from the OpenAFS (Andrew File System). If you are seeing
- this then you chose to include the docs/examples directory in your
- package. One of the example scripts in this directory is a pagsh
+ unresolved dependency for something called /usr/afsws/bin/pagsh.} \\
+ This is a shell from the OpenAFS (Andrew File System). If you are
+ seeing this then you chose to include the docs/examples directory in
+ your package. One of the example scripts in this directory is a pagsh
script. Rpmbuild, when scanning for dependencies, looks at the shebang
line of all packaged scripts in addition to checking shared libraries.
- To avoid this do not package the examples directory. If you are seeing this
- problem you are building a very old bacula package as the examples have been
- removed from the doc packaging.
+ To avoid this do not package the examples directory. If you are seeing
+ this problem you are building a very old bacula package as the examples
+ have been removed from the doc packaging.
\item
\label{faq6}
{\bf I'm building my own rpms because you don't publish for my platform.
- Can I get my packages released to sourceforge for other people to use?} Yes,
- contributions from users are accepted and appreciated. Please examine the
- directory platforms/contrib-rpm in the source code for further information.
+ Can I get my packages released to sourceforge for other people to use?}
+ \\
+ Yes, contributions from users are accepted and appreciated. Please
+ examine the directory platforms/contrib-rpm in the source code for
+ further information.
\item
\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
- allow you to specify build options using GNOME dialog screens. It requires zenity.
+ {\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 allow you to
+ specify build options using GNOME dialog screens. It requires zenity.
\item
\label{faq8}
{\bf I just upgraded from 1.36.x to 1.38.x and now my director daemon
won't start. It appears to start but dies silently and I get a "connection
-refused" error when starting the console. What is wrong?} Beginning with
-1.38 the rpm packages are configured to run the director and storage
-daemons as a non-root user. The file daemon runs as user root and group
-bacula, the storage daemon as user bacula and group disk, and the director
-as user bacula and group bacula. If you are upgrading you will need to
-change some file permissions for things to work. Execute the following
-commands as root:
+refused" error when starting the console. What is wrong?} \\
+ Beginning with 1.38 the rpm packages are configured to run the director
+ and storage daemons as a non-root user. The file daemon runs as user
+ root and group bacula, the storage daemon as user bacula and group disk,
+ and the director as user bacula and group bacula. If you are upgrading
+ you will need to change some file permissions for things to work.
+ Execute the following commands as root:
\footnotesize
\begin{verbatim}
\item
\label{faq9}
{\bf There are a lot of rpm packages. Which packages do I need for
-what?} For a bacula server you need to select the packsge based upon your
+what?} \\
+For a bacula server you need to select the packsge based upon your
preferred catalog database: one of bacula-mysql, bacula-postgresql or
bacula-sqlite. If your system does not provide an mtx package you also
need bacula-mtx to satisfy that dependancy. For a client machine you need
\item {\bf Support for RHEL3/4/5, CentOS 3/4/5, Scientific Linux 3/4/5 and x86\_64}
+ \\
The examples below show
explicit build support for RHEL4 and CentOS 4. Build support
for x86\_64 has also been added.
Install most files to /opt/bacula directory:
--define "single_dir_install 1"
-Supress building the rescue files:
---define "nobuild_rescue 1"
+Build the rescue files:
+--define "build_rescue 1"
\end{verbatim}
\normalsize
However, when attempting to run the daemons, a number of problems
can occur:
\begin{itemize}
-\item [Wrong /var/bacula Permissions]
+\item Wrong /var/bacula Permissions \\
By default, the Director and Storage daemon do not run with
root permission. If the /var/bacula is owned by root, then it
is possible that the Director and the Storage daemon will not
\end{verbatim}
Note: as of 1.38.8 /var/bacula is installed root:bacula with
permissions 770.
-\item [The Storage daemon cannot Access the Tape drive]
+\item The Storage daemon cannot Access the Tape drive \\
This can happen in some older RPM releases where the Storage
daemon ran under userid bacula, group bacula. There are two
ways of fixing this: the best is to modify the /etc/init.d/bacula-sd
projects / bacula / docs / blobdiff