A further problem is the double use of $LOGFILE, as rdrtx1 already mentioned.
The second write opens an already opened file. It might get lost when the writing to the stream continues.
Correct is to write to the already opened stream.
These 2 Users Gave Thanks to MadeInGermany For This Post:
i have following statement in the script
echo -e "$str_XML_col_name:$str_field_type;" >> $i_DC_Key_$i_Tgt_DC_key_Schema
here $i_DC_Key is DC key and $i_Tgt_DC_key are the variables...............
when i ran the script i am getting error rec_merge.sh: $i_DC_Key_$i_Tgt_DC_key_Schema:... (1 Reply)
Hi,
I'm trying to code a simple script (c-shell) on a Solaris box and I'm getting an "Ambiguous" error. These are the lines that cause the error:
On c-shell:
> set var = ""
> @ var = `ls -l`
`ls -l`: Ambiguous
However if I change the second line to:
> set var = `ls -l`
This works... (2 Replies)
Hi everyone, While I was trying to do
DATE=`date +"%Y%m%d_%H%M%S"`
STARTLOG=$TUXSTDDIR/start_$DATE.log
tmboot -y > $STARTLOG 2>&1
I got an error i.e. Ambiguous output redirect error. Here the first part is to boot the account so there is nothing wrong with that.... (6 Replies)
I am trying to run the following script and I am getting an "ambiguous redirect" error. I have checked to make sure that the files are all where I have specified and are read/write as needed. Any ideas?
Note: I have removed the actual path info for privacy sake. I have triple checked to make... (1 Reply)
Hello there,
I'm totally new in bash programming and ran into my first problem.
My script should generate 3 textfiles where the content of the first and the third row are the same in each file. Only the second row is different.
This is what I did in a very simplified explanation:
... (6 Replies)
This script has ambiguous redirect error.
...
cd $HOME
cd folder/work
# search all subfolders in work directory
find -mindepth 1 -maxdepth 1 -type d | while read directory
do
CUR_FOLDER="${directory#"./"}"
cd $CUR_FOLDER
chmod 644 *
for ff in *; do
if ; then
... (5 Replies)
I came across the command string on https://www.unix.com/shell-programming-scripting/141885-awk-removing-data-before-after-pattern.html which was what I was looking for to be able to remove data before a certain pattern. However, outputting the result to a file seems to work on an individual basis... (4 Replies)
Hi,
I need help on following linux bash script. When I linux commands for loop or while loop on individual file it runs great. but now I want the script to run on N number of files so it gives me ambiguous redirect error on line 12 and syntax error on line 22 : (pls help );
#!/bin/bash
#... (16 Replies)
Hi all,
I've been working on a bash script to help with backups that I have to do at work.
One of the lines in the script is supposed to launch an xterm, log into a specific server node and launch a tar backup to tape. This part works ok, but I've been trying to get stdout and stderr to... (2 Replies)
Discussion started by: Exitalterego
2 Replies
LEARN ABOUT CENTOS
gtester
GTESTER(1) User Commands GTESTER(1)NAME
gtester - test running utility
SYNOPSIS
gtester [OPTION...] [testprogram]
DESCRIPTION
gtester is a utility to run unit tests that have been written using the GLib test framework.
When called with the -o option, gtester writes an XML report of the test results, which can be converted into HTML using the gtester-report
utility.
OPTIONS -h, --help
print help and exit
-v, --version
print version information and exit
--g-fatal-warnings
make warnings fatal
-k, --keep-going
continue running after tests failed
-l
list paths of available test cases
-m=MODE
run test cases in MODE, which can be one of:
perf
run performance tests
slow, thorough
run slow tests, or repeat non-deterministic tests more often
quick
do not run slow or performance tests, or do extra repeats of non-deterministic tests (default)
undefined
run test cases that deliberately provoke checks or assertion failures, if implemented (default)
no-undefined
do not run test cases that deliberately provoke checks or assertion failures
-p=TESTPATH
only run test cases matching TESTPATH
-s=TESTPATH
skip test cases matching TESTPATH
--seed=SEEDSTRING
run all test cases with random number seed SEEDSTRING
-o=LOGFILE
write the test log to LOGFILE
-q, --quiet
suppress per test binary output
--verbose
report success per testcase
SEE ALSO gtester-report(1)GLibGTESTER(1)