[Bacula-devel] Patch 2/3: Director job codes in Message resource commands

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

Hi,

our bacula setup includes large numbers of clone jobs which result in a large 
number of messages/mails. For better handling, we now only send mails for non-
clone jobs by using a custom "mail" command for messages that aggregates 
messages of its clones.

This requires the availability of the job codes (especially the "%C" code 
introduced in patch 1/3, see earlier mail) that are known inside the director 
to the messaging system. That is implemented in the attached patch. During 
initialization of the message system (init_msg), the director's job code 
callback is passed to the messaging system, where it is stored in a global 
variable.

I have tested the patch in our scenario and have not seen any negative 
impacts. The calls to the functions that eventually use the job code callback 
-- i.e. ones that execute the mail and operator commands -- are only performed 
from the director side. The callback is initialized with NULL when the message 
system is initialized from the other daemons. I expect the patch to be quite 
safe.

Please feel free to use this patch in upstream or any other bacula editions. 
If you consider the patch for upstream inclusion, I'll be happy to provide a 
documentation patch as well if required. You have my signed FLA.

Thx
   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