Section: Network backup, recovery&verification (8)Updated: 6 December 2009Local indexUp
- Bacula Director
This manual page documents briefly the
Bacula's Director Daemon acts as the controller of the
network backup system: it is responsible for scheduling and
coordinating backups across the network.
Specify the configuration file to use.
Set debug level to nn.
Print timestamp in debug output.
Run in foreground (for debugging).
Set the group/gid to run as.
No signals (for debugging).
Test the configuration file and report errors.
Set the username/uid to run as.
Set verbose mode.
Show version and usage of program.
Tcpwrappers looks for the service name of the bacula daemons in
, and the service names of these daemons is configured to be different from the
The service names are configured to be
(As defined in the bacula-dir.conf.in file)
So the hosts.allow entry has to match
(servername-dir for example) instead of bacula-%component%
This means that if the hosts.allow file has the entry:
you will not be able to run bconsole to connect to the local director!
The entry would have to read:
and this will allow the console to connect to the director.
(The process running is bacula-dir.)