Presumably ${filename[0]} gets expanded into an empty string, and test isn't able to parse that. Remember that unquoted empty strings will simply disappear. Either quote the strings, or append a character before them (or, to be on the safe side, do both -- that's why you frequently see something like if [ X"$string" = X ])
Code:
vnix$ echo $nosuchvariable
vnix$ [ $nosuchvariable -eq 0 -a $nosuchvariable -eq 0 -a $nosuchvariable -eq 0 ]
bash: [: too many arguments
vnix$ [ "$nosuchvariable" -eq 0 -a "$nosuchvariable" -eq 0 -a "$nosuchvariable" -eq 0 ]
bash: [: : integer expression expected
I don't understand why you expect $filename to turn into an array. Your while loop reads one line at a time, and the value you read replaces the previous value for $filename. If you want it to be an array, you need to initialize it in a different way.
Maybe you really mean something like this.
Code:
exec <status.txt
read file1
read file2
read file3
echo "first content of the file is $file1"
echo "second content of the file is $file2"
echo "third content of the file is $file3" # or do you really mean to print "second" twice?
if [ "$file1" -eq 0 -a "$file2" -eq 0 -a "$file3" -eq 0 ]
then
echo "please execute the step 1, then step 2 and then step3"
elif [ "$file1" -eq 0 ]
then
echo "please execute the step 2 and then step3"
elif [ "$file1" -eq 0 -a "$file2" -eq 0 -a "$file3" -ne 0 ]
then
echo "please execute the last step3"
fi
This will still print an error message if not all the input is numeric (that's the "integer expression expected" case in the example above). You might be better off using a case statement instead; it's much less sensitive to the type of input etc than test (aka "[").
I have two scripts:
SCR1 which takes between 5 seconds to 15 minutes and needs to be run every 23 minutes.
SCR2 which needs to be run every 5 minutes but only if SCR1 is not running at that moment.
How can I do this task?
Best Regards
/Hamid (3 Replies)
Hi..
Im using the following script to find whether the present day is monday or not. If it is monday it has to do a specific set of things.
#!/bin/sh
Present_Date=`date`
LOAD_DAY=`date -d "$Present_Date" | cut -d " " -f 1`
echo $LOAD_DAY
if ;then
echo "Monday"
#statements;... (6 Replies)
I am checking one until loop with the following logic
until ||
||||
do
sleep 30
done
before running this i am exporting above variables to SUCCESS.But the loop is running in infinite loop.My requirement is to make the loop run until
all the 3 variables are SUCCESS or any of the 3... (2 Replies)
Hello all! I need help in debugging following script. I have no idea where I am going wrong.
#!/bin/bash
for p1 in A1 TM MP
do
for p2 in A1 TM MP
do
for mp1 in N1 N2
do
for mp2 in N1 N2
do
for mp3 in N1 N2
do
for mp4 in N1 N2
do
for... (7 Replies)
Hi Guys,
Can you please help me to check if my condition is correct.
if &&
then
if ; then
# active
SE_USERID_LUZON_5="A"
elif ; then
# not active
SE_USERID_LUZON_5="D"
${ECHO_CMD}... (3 Replies)
I'm trying to run following code:
while
do
echo "Hello World"
done
but I'm getting error on first line:
./test: line 1: syntax error near unexpected token `('
can anyone please tell me who can i run this loop. Also please tell me what will be syntax of do while loop in case i... (11 Replies)
Hi All,
I need to compare the header of the input files which can be comma demilited, tild(~) or Pipr(|) seperated file.
I am comparing the file header by taking 1st row and comparing it with input row:
Below is the actual code:(ksh script)
if
then
echo $dat >>... (4 Replies)
please follow below code
if ; then
its giving me an error as "test1.sh: line 3: r=$(eval echo '$lck_'$TABLE != "")
if
can anyone tell me how to do inside if condition...with out use any variable..
TIA (6 Replies)
Hi,
I have an if condition on executing it is giving syntax error as below:
--------------------------------------------------------------------------------------
line 61: syntax error in conditional expression
./play_test.sh: line 61: syntax error near `]'
./play_test.sh: line 61: ` if... (2 Replies)
Hi Team,
If condition is not working properly and getting below error
# ./score1.sh
Enter your score ('q' for quit): 102
Enter your score ('q' for quit): q
./score1.sh: line 9: q: integer expression expected
Average is: 102%.
Exit.
Actual code
# Calculate the average of given... (3 Replies)
Discussion started by: Torrid
3 Replies
LEARN ABOUT OPENSOLARIS
xstr
xstr(1) User Commands xstr(1)NAME
xstr - extract strings from C programs to implement shared strings
SYNOPSIS
xstr -c filename [-v] [-l array]
xstr [-l array]
xstr filename [-v] [-l array]
DESCRIPTION
xstr maintains a file called strings into which strings in component parts of a large program are hashed. These strings are replaced with
references to this common area. This serves to implement shared constant strings, which are most useful if they are also read-only.
The command:
example% xstr -c filename
extracts the strings from the C source in name, replacing string references by expressions of the form &xstr[number] for some number. An
appropriate declaration of xstr is prepended to the file. The resulting C text is placed in the file x.c, to then be compiled. The
strings from this file are placed in the strings data base if they are not there already. Repeated strings and strings which are suffixes
of existing strings do not cause changes to the data base.
After all components of a large program have been compiled, a file declaring the common xstr space called xs.c can be created by a command
of the form:
example% xstr
This xs.c file should then be compiled and loaded with the rest of the program. If possible, the array can be made read-only (shared) sav-
ing space and swap overhead.
xstr can also be used on a single file. A command:
example% xstr filename
creates files x.c and xs.c as before, without using or affecting any strings file in the same directory.
It may be useful to run xstr after the C preprocessor if any macro definitions yield strings or if there is conditional code which contains
strings which may not, in fact, be needed. xstr reads from the standard input when the argument `-' is given. An appropriate command
sequence for running xstr after the C preprocessor is:
example% cc -E name.c | xstr -c -
example% cc -c x.c
example% mv x.o name.o
xstr does not touch the file strings unless new items are added; thus make(1S) can avoid remaking xs.o unless truly necessary.
OPTIONS -c filename Take C source text from filename.
-v Verbose: display a progress report indicating where new or duplicate strings were found.
-l array Specify the named array in program references to abstracted strings. The default array name is xstr.
FILES
strings data base of strings
x.c massaged C source
xs.c C source for definition of array "xstr*(rq
/tmp/xs* temp file when xstr filename doesn't touch strings
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO make(1S), attributes(5)BUGS
If a string is a suffix of another string in the data base, but the shorter string is seen first by xstr both strings will be placed in the
data base, when just placing the longer one there would do.
NOTES
Be aware that xstr indiscriminately replaces all strings with expressions of the form &xstr[number] regardless of the way the original C
code might have used the string. For example, you will encounter a problem with code that uses sizeof() to determine the length of a lit-
eral string because xstr will replace the literal string with a pointer that most likely will have a different size than the string's. To
circumvent this problem:
o use strlen() instead of sizeof(); note that sizeof() returns the size of the array (including the null byte at the end),
whereas strlen() doesn't count the null byte. The equivalent of sizeof("xxx") really is (strlen("xxx"))+1.
o use #define for operands of sizeof() and use the define'd version. xstr ignores #define statements. Make sure you run xstr on
filename before you run it on the preprocessor.
You will also encounter a problem when declaring an initialized character array of the form
char x[] = "xxx";
xstr will replace xxx with an expression of the form &xstr[number] which will not compile. To circumvent this problem, use static char *x
= "xxx" instead of static char x[] = "xxx".
SunOS 5.11 14 Sep 1992 xstr(1)