Won't the technique you're using just put the text of the script into
the log file?
(instead of executing the script).
Several ways around this, easiest might be:
(
set -xv
...script body....
) >> log_file 2>&1
On Jul 15, 2008, at 9:21 AM, P T Withington wrote:
I tried to make nightly-go log more of its output by taking the main
body of the script and executing it in a subshell like so:
sh -xv >> ...log file... 2&>1 <<'EOF'
... script body ...
EOF
The idea is that the log file will see the actual steps of the bash
script, not just the output of the ant_call. If I comment out the
step that fetches the source (just as a test), then the script runs
just fine through all the steps and I get the expected failure
message. But if I do an actual build, right after the dist-one
build finishes, the whole script just stops (even though there are
many more steps).
I'm stumped. If no one has any suggestions, I guess I will remove
this bright idea of trying to capture all the output and give up.
--
Don Anderson
Java/C/C++, Berkeley DB, systems consultant
voice: 617-547-7881
email: [EMAIL PROTECTED]
www: http://www.ddanderson.com
