On Thu, 04 Oct 2012 20:44:33 +0800
Wouter van Marle <wouter AT squirrel-systems DOT com> wrote:

> > To not mess with writing the real shell script, consider embedding a
> > call to the shell to your script string, like this:
> > 
> > RunAfterJob = "/bin/sh -c \"/that/cmd ... '%v' | batch\""
> > 
> > 

> That works, thanks for the quick reply!
> 
> Would be nice to have this mentioned in the docs, if it's there I
> totally missed it.
> 
> Writing a real script is of course easy, it's just messy and harder to
> see what's going on if I revisit this which may be years from now.

http://bit.ly/O7z6SU reads this:

"In addition, the command string is parsed then fed to the OS, which
means that the path will be searched to execute your specified command,
but there is no shell interpretation, as a consequence, if you invoke
complicated commands or want any shell features such as redirection or
piping, you must call a shell script and do it inside that script."

I would say the wording is imperfect.
If you can propose a better one, feel free to file a feature request
with http://bugs.bacula.org/

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users