scripts/functions is responsible for initiating the log file.
Users of the log facility are in charge to use, move, delete this log file, now.
1.1 --- a/scripts/crosstool.sh Sat Jun 16 21:44:45 2007 +0000
1.2 +++ b/scripts/crosstool.sh Sat Jun 16 22:23:53 2007 +0000
1.3 @@ -27,13 +27,6 @@
1.4 CT_STAR_DATE=`CT_DoDate +%s%N`
1.5 CT_STAR_DATE_HUMAN=`CT_DoDate +%Y%m%d.%H%M%S`
1.6
1.7 -# Log policy:
1.8 -# - first of all, save stdout so we can see the live logs: fd #6
1.9 -exec 6>&1
1.10 -# - then point stdout to the log file (temporary for now)
1.11 -tmp_log_file="${CT_TOP_DIR}/log.$$"
1.12 -exec >>"${tmp_log_file}"
1.13 -
1.14 # Are we configured? We'll need that later...
1.15 CT_TestOrAbort "Configuration file not found. Please create one." -f "${CT_TOP_DIR}/.config"
1.16
2.1 --- a/scripts/functions Sat Jun 16 21:44:45 2007 +0000
2.2 +++ b/scripts/functions Sat Jun 16 22:23:53 2007 +0000
2.3 @@ -35,6 +35,13 @@
2.4 # shared is not found
2.5 set +o hashall
2.6
2.7 +# Log policy:
2.8 +# - first of all, save stdout so we can see the live logs: fd #6
2.9 +exec 6>&1
2.10 +# - then point stdout to the log file (temporary for now)
2.11 +tmp_log_file="${CT_TOP_DIR}/log.$$"
2.12 +exec >>"${tmp_log_file}"
2.13 +
2.14 # The different log levels:
2.15 CT_LOG_LEVEL_ERROR=0
2.16 CT_LOG_LEVEL_WARN=1
3.1 --- a/scripts/saveSample.sh Sat Jun 16 21:44:45 2007 +0000
3.2 +++ b/scripts/saveSample.sh Sat Jun 16 22:23:53 2007 +0000
3.3 @@ -10,8 +10,9 @@
3.4
3.5 . "${CT_TOP_DIR}/scripts/functions"
3.6
3.7 -exec 6>&1
3.8 +# Don't care about any log file
3.9 exec >/dev/null
3.10 +rm -f "${tmp_log_file}"
3.11
3.12 # Parse the configuration file
3.13 CT_TestOrAbort "Configuration file not found. Please create one." -f "${CT_TOP_DIR}/.config"