On Sunday 22 July 2007 14:09, Arno Lehmann wrote: > > | sh -c cat /etc/bacula/clients.d/*.conf > > IIRC, that was implemented in the current development version. You can > use that syntax everywhere, even in the command line options. > > Sounds good, but I haven't tried it myself. > > > Guess I'll have to take a look at the source. > > I suggest to start with the release notes for the beta versions :-)
Well, the release notes were the place. In the section on changes since 2.1.10, it says: - Config files can be read through a pipe, by specifying a leading | in front of the configuration path/filename. So, I'm assuming it means you do this: @|/path/to/script.sh That wasn't in the devel docs, but I assume it will be there before too long. Thanks for the pointer. I look forward to testing it out. j -- Joshua Kugler Lead System Admin -- Senior Programmer http://www.eeinternet.com PGP Key: http://pgp.mit.edu/ ID 0xDB26D7CE PO Box 80086 -- Fairbanks, AK 99708 -- Ph: 907-456-5581 Fax: 907-456-3111 ------------------------------------------------------------------------- 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
