\begin{description}
-\item [ \verb?--?sysbindir=\lt{}binary-path\gt{}]
- \index[dir]{\verb{--{sysbindir }
+\item [ {-}{-}sysbindir=\lt{}binary-path\gt{}]
+ \index[dir]{{-}{-}sysbindir }
Defines where the Bacula binary (executable) files will be placed during a
{\bf make install} command.
-\item [ \verb?--?sysconfdir=\lt{}config-path\gt{}]
- \index[dir]{\verb{--{sysconfdir }
+\item [ {-}{-}sysconfdir=\lt{}config-path\gt{}]
+ \index[dir]{{-}{-}sysconfdir }
Defines where the Bacula configuration files should be placed during a {\bf
make install} command.
-\item [ \verb?--?enable-smartalloc ]
- \index[dir]{\verb{--{enable-smartalloc }
+\item [ {-}{-}enable-smartalloc ]
+ \index[dir]{{-}{-}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. In this case,
enabled as it helps detect memory leaks. This configuration parameter is used
while building Bacula
-\item [ \verb?--?enable-gnome ]
- \index[dir]{\verb{--{enable-gnome }
+\item [ {-}{-}enable-gnome ]
+ \index[dir]{{-}{-}enable-gnome }
If you have GNOME installed on your computer 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 [ \verb?--?enable-wx-console ]
- \index[console]{\verb{--{enable-wx-console }
+\item [ {-}{-}enable-wx-console ]
+ \index[console]{{-}{-}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. This
install Gnome, as wxWidgets can work with GTK+, Motif or even X11 libraries.
-\item [ \verb?--?enable-tray-monitor ]
- \index[dir]{\verb{--{enable-tray-monitor }
+\item [ {-}{-}enable-tray-monitor ]
+ \index[dir]{{-}{-}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 Bacula daemons, you
must specify this option. Doing so will build everything in the {\bf
src/tray-monitor} directory.
-\item [ \verb?--?enable-static-tools]
- \index[dir]{\verb{--{enable-static-tools }
+\item [ {-}{-}enable-static-tools]
+ \index[dir]{{-}{-}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 problems linking in
or explicitly disable static linking by adding {\bf \verb{--{disable-static-tools}.
-\item [ \verb?--?enable-static-fd]
- \index[fd]{\verb{--{enable-static-fd }
+\item [ {-}{-}enable-static-fd]
+ \index[fd]{{-}{-}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. This
described below is useful for just building a client so that all the other
parts of the program are not compiled.
-\item [ \verb?--?enable-static-sd]
- \index[sd]{\verb{--{enable-static-sd }
+\item [ {-}{-}enable-static-sd]
+ \index[sd]{{-}{-}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 Metal recovery.
-\item [ \verb?--?enable-static-dir]
- \index[dir]{\verb{--{enable-static-dir }
+\item [ {-}{-}enable-static-dir]
+ \index[dir]{{-}{-}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 recovery.
-\item [ \verb?--?enable-static-cons]
- \index[dir]{\verb{--{enable-static-cons }
+\item [ {-}{-}enable-static-cons]
+ \index[dir]{{-}{-}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 useful during a
Bare Metal recovery.
-\item [ \verb?--?enable-client-only]
- \index[console]{\verb{--{enable-client-only }
+\item [ {-}{-}enable-client-only]
+ \index[console]{{-}{-}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 only install
configuration without this option. This option greatly facilitates building a
Client on a client only machine.
-\item [ \verb?--?enable-largefile]
- \index[console]{\verb{--{enable-largefile }
+\item [ {-}{-}enable-largefile]
+ \index[console]{{-}{-}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
revert to 32 bit file addresses by using {\bf \verb{--{disable-largefile}.
-\item [ \verb?--?with-sqlite=\lt{}sqlite-path\gt{}]
- \index[fd]{\verb{--{with-sqlite }
+\item [ {-}{-}with-sqlite=\lt{}sqlite-path\gt{}]
+ \index[fd]{{-}{-}with-sqlite }
This enables use of the SQLite database. The {\bf sqlite-path} is not
normally specified as Bacula looks for the necessary components in a
standard location ({\bf depkgs/sqlite}). See
\ilink{Installing and Configuring SQLite}{_ChapterStart33} chapter of
this manual for more details.
-\item [ \verb?--?with-mysql=\lt{}mysql-path\gt{}]
- \index[fd]{\verb{--{with-mysql }
+\item [ {-}{-}with-mysql=\lt{}mysql-path\gt{}]
+ \index[fd]{{-}{-}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. If this option is not present, the build will
\ilink{Installing and Configuring MySQL}{_ChapterStart} chapter
before proceeding with the configuration.
-\item [ \verb?--?with-postgresql=\lt{}path\gt{}]
- \index[fd]{\verb{--{with-postgresql }
+\item [ {-}{-}with-postgresql=\lt{}path\gt{}]
+ \index[fd]{{-}{-}with-postgresql }
This provides an explicit path to the PostgreSQL libraries if Bacula cannot
find it by default.
-\item [ \verb?--?enable-conio]
- \index[fd]{\verb{--{enable-conio }
+\item [ {-}{-}enable-conio]
+ \index[fd]{{-}{-}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 [ \verb?--?with-readline=\lt{}readline-path\gt{}]
- \index[fd]{\verb{--{with-readline }
+\item [ {-}{-}with-readline=\lt{}readline-path\gt{}]
+ \index[fd]{{-}{-}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
\verb{--{with-readline is specified, readline will be disabled. This option affects
history and editing capability and is no longer supported, so you are on your
own if you have problems.
-\item [ \verb?--?enable-readline]
- \index[fd]{\verb{--{enable-readline }
+\item [ {-}{-}enable-readline]
+ \index[fd]{{-}{-}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 [ \verb?--?with-tcp-wrappers=\lt{}path\gt{}]
- \index[fd]{\verb{--{with-tcp-wrappers }
+\item [ {-}{-}with-tcp-wrappers=\lt{}path\gt{}]
+ \index[fd]{{-}{-}with-tcp-wrappers }
This specifies that you want TCP wrappers (man hosts\_access(5)) compiled in.
The path is optional since Bacula will normally find the libraries in the
standard locations. This option affects the Bacula build. In specifying your
\ilink{Configuring and Testing TCP Wrappers}{wrappers} section
in the Security Chapter.
-\item [ \verb?--?with-working-dir=\lt{}working-directory-path\gt{} ]
- \index[dir]{\verb{--{with-working-dir }
+\item [ {-}{-}with-working-dir=\lt{}working-directory-path\gt{} ]
+ \index[dir]{{-}{-}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
The working directory is not automatically created by the install process, so
you must ensure that it exists before using Bacula for the first time.
-\item [ \verb?--?with-base-port=\lt{}port=number\gt{}]
- \index[dir]{\verb{--{with-base-port }
+\item [ {-}{-}with-base-port=\lt{}port=number\gt{}]
+ \index[dir]{{-}{-}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
IANA. This option is only used to modify the daemon configuration files. You
may also accomplish the same thing by directly editing them later.
-\item [ \verb?--?with-dump-email=\lt{}email-address\gt{}]
- \index[dir]{\verb{--{with-dump-email }
+\item [ {-}{-}with-dump-email=\lt{}email-address\gt{}]
+ \index[dir]{{-}{-}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 [ \verb?--?with-pid-dir=\lt{}PATH\gt{} ]
- \index[dir]{\verb{--{with-pid-dir }
+\item [ {-}{-}with-pid-dir=\lt{}PATH\gt{} ]
+ \index[dir]{{-}{-}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 [ \verb?--?with-subsys-dir=\lt{}PATH\gt{}]
- \index[dir]{\verb{--{with-subsys-dir }
+\item [ {-}{-}with-subsys-dir=\lt{}PATH\gt{}]
+ \index[dir]{{-}{-}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}
subsys directory is not created by the Bacula install, so you must be sure to
create it before using Bacula.
-\item [ \verb?--?with-dir-password=\lt{}Password\gt{}]
- \index[dir]{\verb{--{with-dir-password }
+\item [ {-}{-}with-dir-password=\lt{}Password\gt{}]
+ \index[dir]{{-}{-}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 [ \verb?--?with-fd-password=\lt{}Password\gt{} ]
- \index[fd]{\verb{--{with-fd-password }
+\item [ {-}{-}with-fd-password=\lt{}Password\gt{} ]
+ \index[fd]{{-}{-}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 [ \verb?--?with-sd-password=\lt{}Password\gt{} ]
- \index[sd]{\verb{--{with-sd-password }
+\item [ {-}{-}with-sd-password=\lt{}Password\gt{} ]
+ \index[sd]{{-}{-}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 [ \verb?--?with-dir-user=\lt{}User\gt{} ]
- \index[dir]{\verb{--{with-dir-user }
+\item [ {-}{-}with-dir-user=\lt{}User\gt{} ]
+ \index[dir]{{-}{-}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 specified on
this option.
-\item [ \verb?--?with-dir-group=\lt{}Group\gt{} ]
- \index[dir]{\verb{--{with-dir-group }
+\item [ {-}{-}with-dir-group=\lt{}Group\gt{} ]
+ \index[dir]{{-}{-}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
on this option.
-\item [ \verb?--?with-sd-user=\lt{}User\gt{} ]
- \index[sd]{\verb{--{with-sd-user }
+\item [ {-}{-}with-sd-user=\lt{}User\gt{} ]
+ \index[sd]{{-}{-}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
that the Storage daemon has access to all the devices (tape drives, ...) that
it needs.
-\item [ \verb?--?with-sd-group=\lt{}Group\gt{} ]
- \index[sd]{\verb{--{with-sd-group }
+\item [ {-}{-}with-sd-group=\lt{}Group\gt{} ]
+ \index[sd]{{-}{-}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 [ \verb?--?with-fd-user=\lt{}User\gt{} ]
- \index[fd]{\verb{--{with-fd-user }
+\item [ {-}{-}with-fd-user=\lt{}User\gt{} ]
+ \index[fd]{{-}{-}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
preliminary initializations, it can ``drop'' to the UserId specified on this
option.
-\item [ \verb?--?with-fd-group=\lt{}Group\gt{} ]
- \index[fd]{\verb{--{with-fd-group }
+\item [ {-}{-}with-fd-group=\lt{}Group\gt{} ]
+ \index[fd]{{-}{-}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
\begin{description}
-\item [\verb{--{sysbindir=\lt{}binary-path\gt{}]
- \index[dir]{\verb{--{sysbindir }
+\item [{-}{-}sysbindir=\lt{}binary-path\gt{}]
+ \index[dir]{{-}{-}sysbindir }
D\'efinit l'emplacement des binaires Bacula.
-\item [\verb{--{sysconfdir=\lt{}config-path\gt{}]
- \index[dir]{\verb{--{sysconfdir }
+\item [{-}{-}sysconfdir=\lt{}config-path\gt{}]
+ \index[dir]{{-}{-}sysconfdir }
D\'efinit l'emplacement des fichiers de configuration de Bacula.
-\item [\verb{--{enable-smartalloc ]
- \index[dir]{\verb{--{enable-smartalloc }
+\item [{-}{-}enable-smartalloc ]
+ \index[dir]{{-}{-}enable-smartalloc }
Permet l'inclusion du code Smartalloc de d\'etection de tampons orphelins
(NDT : orphaned buffer). Cette option est vivement recommand\'ee. Nous n'avons
jamais compil\'e sans elle, aussi vous pourriez subir des d\'esagr\'ements si
la recommandons car elle aide \`a d\'etecter les fuites de m\'emoire. Ce
param\`etre est utilis\'e lors de la compilation de Bacula.
-\item [\verb{--{enable-gnome ]
- \index[dir]{\verb{--{enable-gnome }
+\item [{-}{-}enable-gnome ]
+ \index[dir]{{-}{-}enable-gnome }
Si vous avez install\'e GNOME sur votre ordinateur, vous devez sp\'ecifier
cette option pour utiliser la Console graphique GNOME. Vous trouverez les
binaires dans le r\'epertoire {\bf src/gnome-console}.
-\item [\verb{--{enable-wx-console ]
- \index[console]{\verb{--{enable-wx-console }
+\item [{-}{-}enable-wx-console ]
+ \index[console]{{-}{-}enable-wx-console }
Si vous avez install\'e wxWidgets sur votre ordinateur, vous devez
sp\'ecifier cette option pour utiliser la Console graphique wx-console. Vous
trouverez les binaires dans le r\'epertoire {\bf src/wx-console}. Ceci peut
souhaitent pas installer Gnome, car wxWidgets peut fonctionner avec les
librairies GTK+, Motif ou m\^eme X11.
-\item [\verb{--{enable-tray-monitor ]
- \index[console]{\verb{--{enable-tray-monitor }
+\item [{-}{-}enable-tray-monitor ]
+ \index[console]{{-}{-}enable-tray-monitor }
Si vous avez install\'e GTK sur votre ordinateur et utilisez un gestionnaire
de fen\^etre compatible avec le syst\`eme de notification standard FreeDesktop
(tels KDE et GNOME), vous pouvez utiliser une interface graphique pour
surveiller les {\it daemons} Bacula en activant cette option. Les binaires
seront plac\'es dans le r\'epertoire {\bf src/tray-monitor}.
-\item [\verb{--{enable-static-tools]
- \index[console]{\verb{--{enable-static-tools }
+\item [{-}{-}enable-static-tools]
+ \index[console]{{-}{-}enable-static-tools }
Avec cette option, les utilitaires relatifs au Storage Daemon ({\bf bls},
{\bf bextract}, et {\bf bscan}) seront li\'es statiquement, ce qui vous permet
de les utiliser m\^eme si les librairies partag\'ees ne sont pas charg\'ees.
r\'epertoire {\bf src/stored}, assurez-vous d'avoir d\'esactiv\'e cette
option, en ajoutant \'eventuellement {\bf \verb{--{disable-static-tools}.
-\item [\verb{--{enable-static-fd]
- \index[fd]{\verb{--{enable-static-fd }
+\item [{-}{-}enable-static-fd]
+ \index[fd]{{-}{-}enable-static-fd }
Avec cette option, la compilation produira un {\bf static-bacula-fd} en plus
du File Daemon standard. Cette version qui inclut les librairies statiquement
li\'ees est requise pour la reconstruction compl\`ete d'une machine apr\`es
un d\'esastre. Cette option est largement surpass\'ee par l'usage de {\bf
make static-bacula-fd} du r\'epertoire {\bf src/filed}.
-\item [\verb{--{enable-static-sd]
- \index[sd]{\verb{--{enable-static-sd }
+\item [{-}{-}enable-static-sd]
+ \index[sd]{{-}{-}enable-static-sd }
Avec cette option, la compilation produira un {\bf static-bacula-sd} en plus
du Storage Daemon standard. Cette version qui inclut les librairies
statiquement li\'ees peut se r\'ev\'eler utile pour la reconstruction
compl\`ete d'une machine apr\`es un d\'esastre.
-\item [\verb{--{enable-static-dir]
- \index[dir]{\verb{--{enable-static-dir }
+\item [{-}{-}enable-static-dir]
+ \index[dir]{{-}{-}enable-static-dir }
Avec cette option, la compilation produira un {\bf static-bacula-dir} en plus
du Director Daemon standard. Cette version qui inclut les librairies
statiquement li\'ees peut se r\'ev\'eler utile pour la reconstruction
compl\`ete d'une machine apr\`es un d\'esastre.
-\item [\verb{--{enable-static-cons]
- \index[dir]{\verb{--{enable-static-cons }
+\item [{-}{-}enable-static-cons]
+ \index[dir]{{-}{-}enable-static-cons }
Avec cette option, la compilation produira une {\bf static-console} et une
{\bf static-gnome-console} en plus de la Console standard standard. Cette
version qui inclut les librairies statiquement li\'ees peut se r\'ev\'eler
utile pour la reconstruction compl\`ete d'une machine apr\`es un d\'esastre.
-\item [\verb{--{enable-client-only]
- \index[console]{\verb{--{enable-client-only }
+\item [{-}{-}enable-client-only]
+ \index[console]{{-}{-}enable-client-only }
Avec cette option, la compilation produira seulement le File Daemon et les
librairies qui lui sont n\'ecessaires. Aucun des autres {\it daemons}, outils
de stockage, ni la console ne sera compil\'e. De m\^eme, un {\bf make
daemons}, vous devez la d\'esactiver. Cette option facilite grandement la
compilation sur les simples clients.
-\item [\verb{--{enable-largefile]
- \index[console]{\verb{--{enable-largefile }
+\item [{-}{-}enable-largefile]
+ \index[console]{{-}{-}enable-largefile }
Cette option (activ\'ee par d\'efaut) provoque la compilation de Bacula avec
le support d'adressage de fichiers 64 bits s'il est disponible sur votre
syst\`eme. Ainsi Bacula peut lire et \'ecrire des fichiers de plus de 2
GBytes. Vous pouvez d\'esactiver cette option et revenir \`a un adressage de
fichiers 32 bits en utilisant {\bf \verb{--{disable-largefile}.
-\item [\verb{--{with-sqlite=\lt{}sqlite-path\gt{}]
- \index[console]{\verb{--{with-sqlite }
+\item [{-}{-}with-sqlite=\lt{}sqlite-path\gt{}]
+ \index[console]{{-}{-}with-sqlite }
Cette option permet l'utilisation de la base de donn\'ees SQLite. Il n'est,
en principe, pas n\'ecessaire de sp\'ecifier le chemin {\bf sqlite-path} car
Bacula recherche les composants requis dans les r\'epertoires standards ({\bf
\ilink{Installer et Configurer SQLite}{_ChapterStart33} pour plus de
d\'etails.
-\item [\verb{--{with-mysql=\lt{}mysql-path\gt{}]
- \index[console]{\verb{--{with-mysql }
+\item [{-}{-}with-mysql=\lt{}mysql-path\gt{}]
+ \index[console]{{-}{-}with-mysql }
Cette option permet la compilation des services de Catalogue de Bacula. Elle
implique que MySQL tourne d\'ej\`a sur votre syst\`eme, et qu'il soit
install\'e dans le chemin {\bf mysql-path} que vous avez sp\'ecifi\'e. Si
\ilink{Installer and Configurer MySQL}{_ChapterStart}) avant de
proc\'eder \`a la configuration.
-\item [\verb{--{with-postgresql=\lt{}postgresql-path\gt{}]
- \index[console]{\verb{--{with-postgresql }
+\item [{-}{-}with-postgresql=\lt{}postgresql-path\gt{}]
+ \index[console]{{-}{-}with-postgresql }
Cette option d\'eclare un chemin explicite pour les librairies PostgreSQL si
Bacula ne les trouve pas dans le r\'epertoire par d\'efaut.
-\item [\verb{--{enable-conio]
- \index[console]{\verb{--{enable-conio }
+\item [{-}{-}enable-conio]
+ \index[console]{{-}{-}enable-conio }
Cette option permet la compilation d'une petite et l\'eg\`ere routine en
alternative \`a readline, beaucoup plus facile \`a configurer, m\^eme si elle
n\'ecessite aussi les librairies termcap ou ncurses.
-\item [\verb{--{with-readline=\lt{}readline-path\gt{}]
- \index[console]{\verb{--{with-readline }
+\item [{-}{-}with-readline=\lt{}readline-path\gt{}]
+ \index[console]{{-}{-}with-readline }
Sp\'ecifie l'emplacement de {\bf readline}. En principe, Bacula devrait le
trouver s'il est dans une librairie standard. Sinon, et si l'option
\verb{--{with-readline n'est pas renseign\'ee, readline sera d\'esactiv\'e. Cette
d'\'edition. Readline n'est d\'esormais plus support\'e, ce qui signifie que
vous l'utilisez \`a vos risques et p\'erils
-\item [\verb{--{enable-readline]
- \index[console]{\verb{--{enable-readline }
+\item [{-}{-}enable-readline]
+ \index[console]{{-}{-}enable-readline }
Active le support readline. D\'esactiv\'e par d\'efaut en raison de nombreux
probl\`emes de configuration, et parce que le paquettage semble devenir
incompatible.
-\item [\verb{--{with-tcp-wrappers=\lt{}path\gt{}]
- \index[console]{\verb{--{with-tcp-wrappers }
+\item [{-}{-}with-tcp-wrappers=\lt{}path\gt{}]
+ \index[console]{{-}{-}with-tcp-wrappers }
Cette option pr\'ecise que vous voulez TCP wrappers (man hosts\_access(5))
compil\'e dans Bacula. Le chemin est facultatif puisque Bacula devrait, en
principe, trouver les librairies dans les r\'epertoires standards. Cette
\ilink{Configurer et Tester TCP Wrappers}{wrappers} du chapitre
sur la s\'ecurit\'e.
-\item [\verb{--{with-working-dir=\lt{}working-directory-path\gt{}]
- \index[dir]{\verb{--{with-working-dir }
+\item [{-}{-}with-working-dir=\lt{}working-directory-path\gt{}]
+ \index[dir]{{-}{-}with-working-dir }
Cette option est obligatoire et sp\'ecifie un r\'epertoire dans lequel Bacula
peut placer en toute s\'ecurit\'e les fichiers qui resteront d'une
ex\'ecution \`a l'autre. Par exemple, si la base de donn\'ees interne est
automatiquement cr\'e\'e par le processus d'installation, aussi vous devez
veiller \`a ce qu'il existe avant votre premi\`ere utilisation de Bacula.
-\item [\verb{--{with-base-port=\lt{}port=number\gt{}]
- \index[dir]{\verb{--{with-base-port }
+\item [{-}{-}with-base-port=\lt{}port=number\gt{}]
+ \index[dir]{{-}{-}with-base-port }
Bacula a besoin de trois ports TCP/IP pour fonctionner (un pour la Console,
un pour le Storage Daemon et un pour le File Daemon). L'option {\bf
\verb{--{with-baseport} permet d'assigner automatiquement trois ports cons\'ecutifs
Bacula. Vous pouvez \`a tout moment faire cette modification en \'editant
directement ces fichiers.
-\item [\verb{--{with-dump-email=\lt{}email-address\gt{}]
- \index[dir]{\verb{--{with-dump-email }
+\item [{-}{-}with-dump-email=\lt{}email-address\gt{}]
+ \index[dir]{{-}{-}with-dump-email }
Cette option sp\'ecifie l'adresse e-mail qui recevra tous les {\it core dump}.
Cette option n'est en principe utilis\'ee que par les d\'eveloppeurs.
-\item [\verb{--{with-pid-dir=\lt{}PATH\gt{} ]
- \index[dir]{\verb{--{with-pid-dir }
+\item [{-}{-}with-pid-dir=\lt{}PATH\gt{} ]
+ \index[dir]{{-}{-}with-pid-dir }
Ceci pr\'ecise le r\'epertoire de stockage du fichier d'id de processus lors
de l'ex\'ecution. La valeur par d\'efaut est : {\bf /var/run}. Le r\'epertoire
sp\'ecifi\'e ici n'est pas automatiquement cr\'e\'e par le processus
d'installation, aussi vous devez veiller \`a ce qu'il existe avant votre
premi\`ere utilisation de Bacula.
-\item [\verb{--{with-subsys-dir=\lt{}PATH\gt{} ]
- \index[dir]{\verb{--{with-subsys-dir }
+\item [{-}{-}with-subsys-dir=\lt{}PATH\gt{} ]
+ \index[dir]{{-}{-}with-subsys-dir }
Cette option pr\'ecise le r\'epertoire de stockage des fichiers verrous du
sous-syst\`eme lors de l'ex\'ecution. Le r\'epertoire par d\'efaut est {\bf
/var/run/subsys}.Veillez \`a ne pas sp\'ecifier le m\^eme r\'epertoire que
pas automatiquement cr\'e\'e par le processus d'installation, aussi vous devez
veiller \`a ce qu'il existe avant votre premi\`ere utilisation de Bacula.
-\item [\verb{--{with-dir-password=\lt{}Password\gt{} ]
- \index[dir]{\verb{--{with-dir-password }
+\item [{-}{-}with-dir-password=\lt{}Password\gt{} ]
+ \index[dir]{{-}{-}with-dir-password }
Cette option vous permet de pr\'eciser le mot de passe d'acc\`es au Director
(contact\'e, en principe, depuis la console). S'il n'est pas pr\'ecis\'e,
configure en cr\'e\'e un al\'eatoirement.
-\item [\verb{--{with-fd-password=\lt{}Password\gt{} ]
- \index[fd]{\verb{--{with-fd-password }
+\item [{-}{-}with-fd-password=\lt{}Password\gt{} ]
+ \index[fd]{{-}{-}with-fd-password }
Cette option vous permet de pr\'eciser le mot de passe d'acc\`es au File
Daemon (contact\'e, en principe, depuis le Director). S'il n'est pas
pr\'ecis\'e, configure en cr\'e\'e un al\'eatoirement.
-\item [\verb{--{with-sd-password=\lt{}Password\gt{} ]
- \index[sd]{\verb{--{with-sd-password }
+\item [{-}{-}with-sd-password=\lt{}Password\gt{} ]
+ \index[sd]{{-}{-}with-sd-password }
Cette option vous permet de pr\'eciser le mot de passe d'acc\`es au Storage
Daemon (contact\'e, en principe, depuis le File Daemon). S'il n'est pas
pr\'ecis\'e, configure en cr\'e\'e un al\'eatoirement.
-\item [\verb{--{with-dir-user=\lt{}User\gt{} ]
- \index[dir]{\verb{--{with-dir-user }
+\item [{-}{-}with-dir-user=\lt{}User\gt{} ]
+ \index[dir]{{-}{-}with-dir-user }
Cette option vous permet de sp\'ecifier l'UserId utilis\'e pour l'ex\'ecution
du Director. Le Director doit \^etre d\'emarr\'e en tant que root, mais n'a
pas besoin d'\^etre ex\'ecut\'e en tant que root. Apr\`es avoir effectu\'e les
op\'erations d'initialisation pr\'eliminaires, il peut redescendre au niveau
de l'UserId sp\'ecifi\'e dans cette option.
-\item [\verb{--{with-dir-group=\lt{}Group\gt{} ]
- \index[dir]{\verb{--{with-dir-group }
+\item [{-}{-}with-dir-group=\lt{}Group\gt{} ]
+ \index[dir]{{-}{-}with-dir-group }
Cette option vous permet de sp\'ecifier le GroupId utilis\'e pour
l'ex\'ecution du Director. Le Director doit \^etre d\'emarr\'e en tant que
root, mais n'a pas besoin d'\^etre ex\'ecut\'e en tant que root. Apr\`es avoir
effectu\'e les op\'erations d'initialisation pr\'eliminaires, il peut
redescendre au niveau du GroupId sp\'ecifi\'e dans cette option.
-\item [\verb{--{with-sd-user=\lt{}User\gt{} ]
- \index[sd]{\verb{--{with-sd-user }
+\item [{-}{-}with-sd-user=\lt{}User\gt{} ]
+ \index[sd]{{-}{-}with-sd-user }
Cette option vous permet de sp\'ecifier l'UserId utilis\'e pour ex\'ecuter le
Storage Daemon. Le Storage Daemon doit \^etre d\'emarr\'e en tant que root,
mais n'a pas besoin d'\^etre ex\'ecut\'e en tant que root. Apr\`es avoir
utilisez cette option, veillez \`a ce que le Storage Daemon ait acc\`es \`a
tous les p\'eriph\'eriques de stockage dont il a besoin.
-\item [\verb{--{with-sd-group=\lt{}Group\gt{} ]
- \index[sd]{\verb{--{with-sd-group }
+\item [{-}{-}with-sd-group=\lt{}Group\gt{} ]
+ \index[sd]{{-}{-}with-sd-group }
Cette option vous permet de sp\'ecifier le GroupId utilis\'e pour ex\'ecuter
le Storage Daemon. Le Storage Daemon doit \^etre d\'emarr\'e en tant que
root, mais n'a pas besoin d'\^etre ex\'ecut\'e en tant que root. Apr\`es avoir
effectu\'e les op\'erations d'initialisation pr\'eliminaires, il peut
redescendre au niveau du GroupId sp\'ecifi\'e dans cette option.
-\item [\verb{--{with-fd-user=\lt{}User\gt{} ]
- \index[fd]{\verb{--{with-fd-user }
+\item [{-}{-}with-fd-user=\lt{}User\gt{} ]
+ \index[fd]{{-}{-}with-fd-user }
Cette option vous permet de sp\'ecifier l'UserId utilis\'e pour ex\'ecuter le
File Daemon. Le File Daemon doit \^etre d\'emarr\'e et, dans la plupart des
cas, ex\'ecut\'e en tant que root, de sorte que cette option n'est utilis\'ee
les op\'erations d'initialisation pr\'eliminaires, il peut redescendre au
niveau de l'UserId sp\'ecifi\'e dans cette option.
-\item [\verb{--{with-fd-group=\lt{}Group\gt{} ]
- \index[fd]{\verb{--{with-fd-group }
+\item [{-}{-}with-fd-group=\lt{}Group\gt{} ]
+ \index[fd]{{-}{-}with-fd-group }
Cette option vous permet de sp\'ecifier le GroupId utilis\'e pour ex\'ecuter
le File Daemon. Le File Daemon doit \^etre d\'emarr\'e et, dans la plupart
des cas, ex\'ecut\'e en tant que root, de sorte que cette option n'est
\begin{description}
-\item [ \verb:--:sysbindir=\lt{}binary-path\gt{}]
- \index[dir]{\verb:--:sysbindir }
+\item [ {-}{-}sysbindir=\lt{}binary-path\gt{}]
+ \index[dir]{{-}{-}sysbindir }
Defines where the Bacula binary (executable) files will be placed during a
{\bf make install} command.
-\item [ \verb:--:sysconfdir=\lt{}config-path\gt{}]
- \index[dir]{\verb:--:sysconfdir }
+\item [ {-}{-}sysconfdir=\lt{}config-path\gt{}]
+ \index[dir]{{-}{-}sysconfdir }
Defines where the Bacula configuration files should be placed during a {\bf
make install} command.
-\item [ \verb:--:enable-smartalloc ]
- \index[dir]{\verb:--:enable-smartalloc }
+\item [ {-}{-}enable-smartalloc ]
+ \index[dir]{{-}{-}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. In this case,
enabled as it helps detect memory leaks. This configuration parameter is used
while building Bacula
-\item [ \verb:--:enable-gnome ]
- \index[dir]{\verb:--:enable-gnome }
+\item [ {-}{-}enable-gnome ]
+ \index[dir]{{-}{-}enable-gnome }
If you have GNOME installed on your computer 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 [ \verb:--:enable-wx-console ]
- \index[console]{\verb:--:enable-wx-console }
+\item [ {-}{-}enable-wx-console ]
+ \index[console]{{-}{-}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. This
install Gnome, as wxWidgets can work with GTK+, Motif or even X11 libraries.
-\item [ \verb:--:enable-tray-monitor ]
- \index[dir]{\verb:--:enable-tray-monitor }
+\item [ {-}{-}enable-tray-monitor ]
+ \index[dir]{{-}{-}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 Bacula daemons, you
must specify this option. Doing so will build everything in the {\bf
src/tray-monitor} directory.
-\item [ \verb:--:enable-static-tools]
- \index[dir]{\verb:--:enable-static-tools }
+\item [ {-}{-}enable-static-tools]
+ \index[dir]{{-}{-}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 problems linking in
or explicitly disable static linking by adding {\bf \verb:--:disable-static-tools}.
-\item [ \verb:--:enable-static-fd]
- \index[fd]{\verb:--:enable-static-fd }
+\item [ {-}{-}enable-static-fd]
+ \index[fd]{{-}{-}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. This
described below is useful for just building a client so that all the other
parts of the program are not compiled.
-\item [ \verb:--:enable-static-sd]
- \index[sd]{\verb:--:enable-static-sd }
+\item [ {-}{-}enable-static-sd]
+ \index[sd]{{-}{-}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 Metal recovery.
-\item [ \verb:--:enable-static-dir]
- \index[dir]{\verb:--:enable-static-dir }
+\item [ {-}{-}enable-static-dir]
+ \index[dir]{{-}{-}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 recovery.
-\item [ \verb:--:enable-static-cons]
- \index[dir]{\verb:--:enable-static-cons }
+\item [ {-}{-}enable-static-cons]
+ \index[dir]{{-}{-}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 useful during a
Bare Metal recovery.
-\item [ \verb:--:enable-client-only]
- \index[console]{\verb:--:enable-client-only }
+\item [ {-}{-}enable-client-only]
+ \index[console]{{-}{-}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 only install
configuration without this option. This option greatly facilitates building a
Client on a client only machine.
-\item [ \verb:--:enable-largefile]
- \index[console]{\verb:--:enable-largefile }
+\item [ {-}{-}enable-largefile]
+ \index[console]{{-}{-}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
revert to 32 bit file addresses by using {\bf \verb:--:disable-largefile}.
-\item [ \verb:--:with-sqlite=\lt{}sqlite-path\gt{}]
- \index[fd]{\verb:--:with-sqlite }
+\item [ {-}{-}with-sqlite=\lt{}sqlite-path\gt{}]
+ \index[fd]{{-}{-}with-sqlite }
This enables use of the SQLite database. The {\bf sqlite-path} is not
normally specified as Bacula looks for the necessary components in a
standard location ({\bf depkgs/sqlite}). See
\ilink{Installing and Configuring SQLite}{_ChapterStart33} chapter of
this manual for more details.
-\item [ \verb:--:with-mysql=\lt{}mysql-path\gt{}]
- \index[fd]{\verb:--:with-mysql }
+\item [ {-}{-}with-mysql=\lt{}mysql-path\gt{}]
+ \index[fd]{{-}{-}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. If this option is not present, the build will
\ilink{Installing and Configuring MySQL}{_ChapterStart} chapter
before proceeding with the configuration.
-\item [ \verb:--:with-postgresql=\lt{}path\gt{}]
- \index[fd]{\verb:--:with-postgresql }
+\item [ {-}{-}with-postgresql=\lt{}path\gt{}]
+ \index[fd]{{-}{-}with-postgresql }
This provides an explicit path to the PostgreSQL libraries if Bacula cannot
find it by default.
-\item [ \verb:--:with-python=\lt{}path\gt{}]
- \index[fd]{\verb:--:with-python }
+\item [ {-}{-}with-python=\lt{}path\gt{}]
+ \index[fd]{{-}{-}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
\ilink{Python chapter}{_ChapterStart60} for the details of using
Python scripting.
-\item [ \verb:--:enable-conio]
- \index[fd]{\verb:--:enable-conio }
+\item [ {-}{-}enable-conio]
+ \index[fd]{{-}{-}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 [ \verb:--:with-readline=\lt{}readline-path\gt{}]
- \index[fd]{\verb:--:with-readline }
+\item [ {-}{-}with-readline=\lt{}readline-path\gt{}]
+ \index[fd]{{-}{-}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
\verb:--:with-readline is specified, readline will be disabled. This option affects
history and editing capability and is no longer supported, so you are on your
own if you have problems.
-\item [ \verb:--:enable-readline]
- \index[fd]{\verb:--:enable-readline }
+\item [ {-}{-}enable-readline]
+ \index[fd]{{-}{-}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 [ \verb:--:with-tcp-wrappers=\lt{}path\gt{}]
- \index[fd]{\verb:--:with-tcp-wrappers }
+\item [ {-}{-}with-tcp-wrappers=\lt{}path\gt{}]
+ \index[fd]{{-}{-}with-tcp-wrappers }
This specifies that you want TCP wrappers (man hosts\_access(5)) compiled in.
The path is optional since Bacula will normally find the libraries in the
standard locations. This option affects the Bacula build. In specifying your
\ilink{Configuring and Testing TCP Wrappers}{wrappers} section
in the Security Chapter.
-\item [ \verb:--:with-working-dir=\lt{}working-directory-path\gt{} ]
- \index[dir]{\verb:--:with-working-dir }
+\item [ {-}{-}with-working-dir=\lt{}working-directory-path\gt{} ]
+ \index[dir]{{-}{-}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
The working directory is not automatically created by the install process, so
you must ensure that it exists before using Bacula for the first time.
-\item [ \verb:--:with-base-port=\lt{}port=number\gt{}]
- \index[dir]{\verb:--:with-base-port }
+\item [ {-}{-}with-base-port=\lt{}port=number\gt{}]
+ \index[dir]{{-}{-}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
IANA. This option is only used to modify the daemon configuration files. You
may also accomplish the same thing by directly editing them later.
-\item [ \verb:--:with-dump-email=\lt{}email-address\gt{}]
- \index[dir]{\verb:--:with-dump-email }
+\item [ {-}{-}with-dump-email=\lt{}email-address\gt{}]
+ \index[dir]{{-}{-}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 [ \verb:--:with-pid-dir=\lt{}PATH\gt{} ]
- \index[dir]{\verb:--:with-pid-dir }
+\item [ {-}{-}with-pid-dir=\lt{}PATH\gt{} ]
+ \index[dir]{{-}{-}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 [ \verb:--:with-subsys-dir=\lt{}PATH\gt{}]
- \index[dir]{\verb:--:with-subsys-dir }
+\item [ {-}{-}with-subsys-dir=\lt{}PATH\gt{}]
+ \index[dir]{{-}{-}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}
subsys directory is not created by the Bacula install, so you must be sure to
create it before using Bacula.
-\item [ \verb:--:with-dir-password=\lt{}Password\gt{}]
- \index[dir]{\verb:--:with-dir-password }
+\item [ {-}{-}with-dir-password=\lt{}Password\gt{}]
+ \index[dir]{{-}{-}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 [ \verb:--:with-fd-password=\lt{}Password\gt{} ]
- \index[fd]{\verb:--:with-fd-password }
+\item [ {-}{-}with-fd-password=\lt{}Password\gt{} ]
+ \index[fd]{{-}{-}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 [ \verb:--:with-sd-password=\lt{}Password\gt{} ]
- \index[sd]{\verb:--:with-sd-password }
+\item [ {-}{-}with-sd-password=\lt{}Password\gt{} ]
+ \index[sd]{{-}{-}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 [ \verb:--:with-dir-user=\lt{}User\gt{} ]
- \index[dir]{\verb:--:with-dir-user }
+\item [ {-}{-}with-dir-user=\lt{}User\gt{} ]
+ \index[dir]{{-}{-}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 specified on
this option.
-\item [ \verb:--:with-dir-group=\lt{}Group\gt{} ]
- \index[dir]{\verb:--:with-dir-group }
+\item [ {-}{-}with-dir-group=\lt{}Group\gt{} ]
+ \index[dir]{{-}{-}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
on this option.
-\item [ \verb:--:with-sd-user=\lt{}User\gt{} ]
- \index[sd]{\verb:--:with-sd-user }
+\item [ {-}{-}with-sd-user=\lt{}User\gt{} ]
+ \index[sd]{{-}{-}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
that the Storage daemon has access to all the devices (tape drives, ...) that
it needs.
-\item [ \verb:--:with-sd-group=\lt{}Group\gt{} ]
- \index[sd]{\verb:--:with-sd-group }
+\item [ {-}{-}with-sd-group=\lt{}Group\gt{} ]
+ \index[sd]{{-}{-}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 [ \verb:--:with-fd-user=\lt{}User\gt{} ]
- \index[fd]{\verb:--:with-fd-user }
+\item [ {-}{-}with-fd-user=\lt{}User\gt{} ]
+ \index[fd]{{-}{-}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
preliminary initializations, it can ``drop'' to the UserId specified on this
option.
-\item [ \verb:--:with-fd-group=\lt{}Group\gt{} ]
- \index[fd]{\verb:--:with-fd-group }
+\item [ {-}{-}with-fd-group=\lt{}Group\gt{} ]
+ \index[fd]{{-}{-}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
projects / bacula / docs / commitdiff