05-18-2008
Without seeing the whole script, it's very hard to say. It's not uncommon for this error message to be caused by a quoting problem somewhere pretty far from the line indicated by the error message; if a misplaced quote hides a "fi" from the shell, it will still be looking for it when it gets to a "done" much later, and complain about the "done". (You seem to be missing a "do" after "while [ $semi2 -le 90 ]"; perhaps this is related.)
I hope you have indentation in your actual script to show the structure, especially if it's that long. You might want to use
code tags when posting code snippets in the future.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have a file called test.dat which contains
a b
I have written a shell script called test.sh
for i in `cat test.dat`
do
echo $i
done
When i run this script using
sh test.sh
I get this message -
test.sh: syntax error at line 6: `end of file' unexpected
What is the... (3 Replies)
Discussion started by: debojyoty
3 Replies
2. Shell Programming and Scripting
Hi
Can any one help, I'm trying to run a script that beeps out the ip address from the PC internal speaker with the following script. It keeps throwing the error "Syntax error: Bad for loop variable" on line 16. I know its picking up the IP ADDRESS correctly. Any ideas on whats wrong. I'm... (3 Replies)
Discussion started by: dman
3 Replies
3. Shell Programming and Scripting
hi,
I have to use for loop in my script. The below code is providing an output,
1,2,3,4,5..n. But i need to display the values one by one eg: it has to display the first value then exit from the loop and display the second value then exit till n(last value).
for i in 1,2,3,4,5..n
do ... (2 Replies)
Discussion started by: sreelu
2 Replies
4. Shell Programming and Scripting
Hello forum,
I hope my problem is easy to solve for someone in here!
My main task is to copy a large amount of imap-accounts from one server to another. There is a tool (Perl) called imapsync which does the job exellent. Unfortunately I'm only able to run it on one account at a time.
After... (3 Replies)
Discussion started by: primaxx
3 Replies
5. UNIX for Dummies Questions & Answers
%%%%% (3 Replies)
Discussion started by: lucasvs
3 Replies
6. Shell Programming and Scripting
I'm getting an error while running this script. Need help.
set -x verbose #echo on
clear #clear the screen
USERNAME="bbb"
PASSWORD="password"
SERVER="192.168.1.100"
WAIT_TIME=300
FILE_PATH="/home/users/xxx/MMM" # local directory to pickup *.dat file
REMOTE_PATH="/Drop_off/xxx/yyy" #... (17 Replies)
Discussion started by: clgz2002
17 Replies
7. Shell Programming and Scripting
I am trying to run a menu option though IF loops. I keep getting errors not allowed the menu to be processed correctly. Currently it will accept the first 2 statements but then crash on the 3rd. The 2nd and 3rd have the same syntax, so I do not understand why it breaks.
#!/bin/bash
while... (4 Replies)
Discussion started by: Ironguru
4 Replies
8. UNIX for Dummies Questions & Answers
can some one please tell me what is the problem with my syntax:confused:
I have 100 files in one folder
1. want to read each of the line by line
2. calculate their number of the words between the first word and the last word of each line
3. create file for each file with number of words... (8 Replies)
Discussion started by: A-V
8 Replies
9. UNIX for Dummies Questions & Answers
I am using simple for loop, but getting syntax error when I run the code
code
#!/bin/ksh
pls enter number
read n
for(i=1; i<=n; i++)
do
echo $i
done
syntax error
+ pls enter number
+ read n (5 Replies)
Discussion started by: stew
5 Replies
10. Shell Programming and Scripting
I have a shell script which has this while loop line
"while read tblName xx; do..."
I understand how while loop works but don't know what does this xx stands for? (1 Reply)
Discussion started by: later_troy
1 Replies
LEARN ABOUT CENTOS
error::pass1
ERROR::PASS1(7stap) ERROR::PASS1(7stap)
NAME
error::pass1 - systemtap pass-1 errors
DESCRIPTION
Errors that occur during pass 1 (parsing) usually mean a basic syntax error of some sort occurred in the systemtap script. There are sev-
eral classes of problems possible:
plain syntax error
The systemtap script parser detects a large variety of errors, such as missing operands, bad punctuation. It tries to list what
kinds of tokens it was expecting to see, and will show the region of the source code with the problem. Please review the stap(1)
man page and/or the tutorial, to correct the script's syntax.
grammar ambiguities
There is at least one known ambiguity in the systemtap grammar. It relates to the optionality of ; (semicolon) separators between
statements, and the ++ and -- increment/decrement operators. If the parser indicates an error, consider adding some explicit ; sep-
arators between nearby statements and try again.
missing command line arguments
A systemtap script that uses the $N and @N constructs for substituting in command-line options may fail if not enough options were
given on the stap command line.
compatibility changes
Some versions of systemtap have changed the language incompatibly, for example by adding the try/catch keywords for exception han-
dling. In such cases, rerun systemtap with the --compatibility=VERSION option, substituting the last systemtap version where your
script was known to work. You may also check the release-history NEWS file for compatibility changes.
GATHERING MORE INFORMATION
Increasing the verbosity of pass-1 with an option such as --vp 1 can help pinpoint the problem.
SEE ALSO
stap(1),
error::reporting(7stap)
ERROR::PASS1(7stap)