Hi, 10.12.2007 12:58,, Bastian Friedrich wrote:: > Hi, > > The "run" statements in job definitions seem to be a great way to accomplish > backing up multiple distinguished subsets of a file system. By adding FileSet > parameters, one job can back up a machine and still keep information about > more abstract system components.
I don't think I understand what you want to do here, so if you feel like it, a more detailed explanation (perhaps with an example ;-) would be nice. > Yet, preprocessing parts of these subsets with RunScript statements (and its > relatives: Run Before Job, Run After Job, ...) seems to be a problem; > the "%<character>" substitutes don't include a fileset reference. Right. > Unfortunately, the relevant low level/source structures don't allow for a > simple adding of such a reference, as far as I can see... > > Is there any chance to access the current file set name in a run script? I think adding that to the job codes' interpretation should be reasonably easy. Have a look into src/lib/util.c and you'll find the function edit_job_codes(). That's where the work is done. Getting the name of the current file set might be a bit difficult; the JCR contains a pointer to a JOB object, which in turn contains a pointer to the fileset. If you have problems accessing the file set name, you should ask on the -devel mailing list. That's where you send your patch, too ;-) Hope this helps, Arno > Thx, best, > Bastian > -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
