[Bacula-devel] job code variables in environment?

[Bastian F. <bas...@co...>]

Hi,

while dealing with the topics mentioned in my last two posts (client side run 
scripts, and client side file lists) I had some problems getting some required 
information from the bacula services to my scripts. These problems were solved 
with the sent patches, however.

While working on that topic, I thought about providing the required 
information not (only) via command line arguments (using the %<whatever> job 
codes), but also additionally via the environment, setting appropriate 
variables for all the job codes that bacula knows. The costs of doing so would 
be the creation of a number of environment variables during script execution.

I created an appropriate patch for the "open_bpipe" function; the patch is not 
finished, however (which is why I do not send it here yet). Would you be 
interested in me providing a more complete version of that patch (and consider 
taking it upstream)? My current patch only provides environment variables for 
the "\|script" fileset config statements; a full version would, of course, 
provide these variables for other scripts, e.g., run scripts.

As I have solved my problems using a different approach now, I'll only 
create/send a patch if there's a chance for upstream acceptance.

Thx & best regards
   Bastian

-- 
Collax GmbH . Basler Str. 115a . 79115 Freiburg . Germany
p: +49 (0) 89-990 157-28	www.collax.com

Geschäftsführer: Bernd Bönte, Boris Nalbach
AG München HRB 173695. Ust.-IdNr: DE270819312