On Friday 18 January 2008 10.38:38 Alexander Kolesnik wrote: > Hello Kern, > > > Bacula runs the *program* that you specify. In your command, you are > > using > > *shell* commands (>>) and the OS does not know how to interpret shell > > > commands. So if you want to use shell commands (as you did), you must > > run a shell or a shell script. With the Bacula Run scripts, you are > > talking directly to the system and not to a shell. If you don't > > understand what all the above means, someone on the list can probably > > help you.
The "wrapper" script is machine dependent, but if you look at the manual as I suggested, you will see an example of doing it inline on the RunxxxScript command -- you simply insert a call to the shell, BUT you need appropriate escaping of the shell arguments. > > I understand what you mean, thanks. However, it's not very convinient > to put such a simple wrapper script on every client machine.. Perhaps, > you could implement a feature to feed script content from the director > to the client? I think there are much higher priority items given the fact that what you want to do can be done on the Run Script command line or alternative in a shell file. Kern ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
