Hi all,
I noticed in the Bacula User's guide there is a configure option (when
building Bacula from Source):
--enable-client-only
>
Described as:
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 make install will then only install the
> File daemon. To cause all daemons to be built, you will need to do a
> configuration without this option. This option greatly facilitates building
> a Client on a client only machine.
>
This is fantastic. But why is there also not an equivalent option for
building only the Storage Daemon? For example, I will be running the Storage
Daemon only on a Debian Linux machine. The Storage Daemon need not
communicate directly with the Catalog (e.g., PostgreSQL database) so I don't
want to be required to build an entire Bacula system (e.g. including
requisite database) for my Debian machine which will only run the Storage
Daemon.
Thanks for shedding any light on this!
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
