John Drescher wrote:
> > however, i would prefer to have all these files on the director host,
> > and include them based on the job running.
> >
> > something like:
> >
> >   File = "</etc/bacula/${jobname}_exclude.conf"
> >
> Yes, that works and it is in the manual.

I don't think variable expansion works in this context (which is how I
interpreted the example).  Bacula complains:

Fatal error: Cannot open included
file: /usr/local/etc/bacula/filesets/${jobname}_exclude.conf. ERR=No
such file or directory

As you can see, bacula thinks ${jobname} is the literal file name.  The
same thing happens for the % character substitution [1] and the volume
label variables [2].

Using variables to include external files would be a huge convenience.

[1]
http://bacula.org/rel-manual/Configuring_Director.html#character_substitution
[2] http://bacula.org/rel-manual/Variable_Expansion.html
Dane
-- 
Dane Miller
Systems Administrator
Great Schools, Inc
http://greatschools.net


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to