On Mon, Oct 24, 2011 at 9:42 AM, Appelt, Uwe <uwe.app...@nct-heidelberg.de> wrote: > Hi Peter, > > thanks a lot for your quick reply. However "&>" doesn't > seem to work as well. Also, I do have to admit that two different > "doesn't work" exist. > > Notations that are not accepted during parsing of toolxy.xml: > &> > \&> > \\&> > > Notations that are accepted, but don't produce any content written > to "$logFile": > &> > &> > &> > > Any other suggestions? > > Cheers, > Uwe
Curious. Well, at least you seem to have valid XML now (double check this with an XML validator). Does Galaxy capture anything in the "info" box (stdout)? There are some variants like 2>&1 for redirecting stderr to stdout, try combining that with > logfile. My *guess* however is the interpreter="bash" may be to blame, try this after ensuring the script is executable and on the path or fully specified: <command>$myScript &> $logFile</command> Peter ___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list: http://lists.bx.psu.edu/listinfo/galaxy-dev To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
