would normally use, and each developer/user may modify them to suit his needs.
You should find additional useful examples in this directory as well.
-The {\bf \verb:--:enable-conio} or {\bf \verb:--:enable-readline} options are
+The {\bf \lstinline:--:enable-conio} or {\bf \lstinline:--:enable-readline} options are
useful because they provide a command line history, editing capability for the
Console program and tab completion on various option. If you have included
either option in the build, either the {\bf termcap} or the {\bf ncurses}
On some systems such as Mandriva, readline tends to
gobble up prompts, which makes it totally useless. If this happens to you, use
the disable option, or if you are using version 1.33 and above try using {\bf
-\verb:--:enable-conio} to use a built-in readline replacement. You will still need
+\lstinline:--:enable-conio} to use a built-in readline replacement. You will still need
either the termcap or the ncurses library, but it is unlikely that the {\bf conio}
package will gobble up prompts.
using them without having the shared libraries loaded. If you have
problems linking in the {\bf src/stored} directory, make sure you have
not enabled this option, or explicitly disable static linking by adding
- {\bf \verb:--:disable-static-tools}.
+ {\bf \lstinline:--:disable-static-tools}.
\item [ {-}{\-}enable-static-fd]
\index[general]{{-}{\-}enable-static-fd}
statically linked libraries and is required for the Bare Metal recovery.
This option is largely superseded by using {\bf make static-bacula-fd}
from with in the {\bf src/filed} directory. Also, the {\bf
- \verb:--:enable-client-only} option described below is useful for just
+ \lstinline:--:enable-client-only} option described below is useful for just
building a client so that all the other parts of the program are not
compiled.
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
- revert to 32 bit file addresses by using {\bf \verb:--:disable-largefile}.
+ revert to 32 bit file addresses by using {\bf \lstinline:--:disable-largefile}.
\item [ {-}{\-}disable-nls]
\index[general]{{-}{\-}disable-nls}
\index[general]{{-}{\-}with-baseport}
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
+ \lstinline:--:with-baseport} option will automatically assign three ports beginning at
the base port address specified. You may also change the port number in the
resulting configuration files. However, you need to take care that the
numbers correspond correctly in each of the three daemon configuration
\end{description}
Note, many other options are presented when you do a {\bf ./configure
-\verb:--:help}, but they are not implemented.
+\lstinline:--:help}, but they are not implemented.
\section{Recommended Options for Most Systems}
\index[general]{Systems!Recommended Options for Most}
If you want to install Bacula in an installation directory rather than run it
out of the build directory (as developers will do most of the time), you
-should also include the \verb:--:sbindir and \verb:--:sysconfdir options with appropriate
+should also include the \lstinline:--:sbindir and \lstinline:--:sysconfdir options with appropriate
paths. Neither are necessary if you do not use "make install" as is the case
for most development work. The install process will create the sbindir and
sysconfdir if they do not exist, but it will not automatically create the
./configure}.
Since the File daemon does not access the Catalog database, you can remove
-the {\bf \verb:--:with-mysql} or {\bf \verb:--:with-sqlite} options, then
-add {\bf \verb:--:enable-client-only}. This will compile only the
+the {\bf \lstinline:--:with-mysql} or {\bf \lstinline:--:with-sqlite} options, then
+add {\bf \lstinline:--:enable-client-only}. This will compile only the
necessary libraries and the client programs and thus avoids the necessity
of installing one or another of those database programs to build the File
daemon. With the above option, you simply enter {\bf make} and just the
\index[general]{Installing Tray Monitor}
The Tray Monitor is already installed if you used the {\bf
-\verb:--:enable-tray-monitor} configure option and ran {\bf make install}.
+\lstinline:--:enable-tray-monitor} configure option and ran {\bf make install}.
As you don't run your graphical environment as root (if you do, you should
change that bad habit), don't forget to allow your user to read {\bf