On 06/09/12 16:39, Simone Caronni wrote:
>> You could also use multiple ClientRunBefore statements in the config file. 
>> Personally I would still prefer a script in the client.
> On my setups I use the opposite. If you need to add a line to the
> script, you need to copy the same script over all the clients. With
> multiple lines, maybe you can change just one line in the Job
> Definition.
>
> Don't know how many you have in your backup infrastructure, but that's
> not feasible at all in our setup; especially because the clients and
> daemons are separated by firewalls and do not allow easy copying
> everywhere.
Thank you everybody for your answers,
I now use ";" to separate shell commands on one line and if I reach the
limit then add more ClientRunBefore commands.
As mentioned by Simone, it's not easy to deploy scripts to 100s of
machines, so... :)


>
> Regards,
> --Simone
>
>
>



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users