I'm instead using a shell script to build the client defs. It's actually easier and more flexible. You simply include a shell script in your bacula-dir.conf with the @| syntax (like so:
@|/etc/bacula/jobs/alljobs.bash A template approach for clients isn't all that useful because almost all the client information is individual from one client to the next. -----Original Message----- From: Alex Huth [mailto:a.h...@tmr.net] Sent: Thursday, July 08, 2010 1:43 AM To: bacula-users@lists.sourceforge.net Subject: [Bacula-users] Client defs Hello! Is it possible to build Client defaults like JobDefaults? I have nothing found in the doc and google. This would be good when having lots of clients. Greetings Alex Huth ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
