On Mar 19, 2007, at 6:59 AM, Jorj Bauer wrote:
> What: The ability to read a configuration file as stdout from an
> executable
>
> Why: The configuration files (particularly for the Director) are very
> complex. In my case I find it easier to have a program generate them
> from meta-information about the clients.
>
> Notes:
>
> The attached patch implements this. It's a simple change to lex.c, and
> functions globally: if the first character of any configuration file's
> name is a pipe ("|"), then the rest of the "filename" is considered to
> be the path to an executable. The program is run, stdout is read, and
> the output is the configuration file.
>
> For example, starting the director like this:
>
> # bacula-dir -c '|/usr/local/sbin/generate-dir-config'
>
> ... would cause it to run /usr/local/sbin/generate-dir-config to
> generate a new configuration file.
Hey, that sounds pretty useful. When you say "globally", I assume you
mean that I can just toss a similar line into bacula-dir to generate
a subset of the configuration data from a script?
--
--Darien A. Hager
[EMAIL PROTECTED]
Mobile: (206) 734-5666
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
