I will appreciate help is this matter. i am getting this error (./getwind.scr: line 41: syntax error: unexpected end of file) in the following script :
i highly appreciate your help.
Thanks,
Peeriich
Last edited by Franklin52; 08-21-2010 at 05:19 AM..
Reason: Please use code tags
Hi,
I need ur help is this matter, i have th ebelow script, and i keep getting this error: syntax error: unexpected end of file
affectedRow=`cat dbOutput.log | grep "1 row affected"`
echo "affectedRow : $affectedRow"
if ; then
echo "Look to the next OMCDB"
... (10 Replies)
I have a script that's failing
./zzmaster.sh: line 2: syntax error: unexpected end of file
There are 4 scripts total involved. The first 'znocc0.sh' essentially curls a page then does some sed sequences...
#!/bin/sh
#GET SENTINAL INFO
curl -b z0cookie.txt -L -k -e... (2 Replies)
Hi,
I have problem in constructing "IF" condition.
The below code throws "tst.sh: line 10: syntax error: unexpected end of file"
#!/bin/ksh
test=9
echo $test
if ]
then
echo "in"
fi
echo "end"
exit 0
Actually, i want to check whether the variable $test is empty or null.
... (5 Replies)
Hi,
I am newbie to UNIX scripting. I am facing this error "syntax error: unexpected end of file" while executing the following script:
------
a=$1
if
then
sqlplus -s prospect_stg/prospect_stg@mdmpt <<END
insert into bckup_marc_parameter_lookup select * from... (6 Replies)
Hi all,
I am very new to programming and even newer to this forum as well, so I apologize if this should have been in the Newbie category, but...
I am currently trying to figure out Shell Scripting and am running into problems early. Not having taken any kind of programming class, I am not even... (2 Replies)
I am new to unix, so thank u for ur patience
I try to make it work (to duplicate two first columns in several files):
#!/bin/bash
for i in `seq 2 5`
do
awk `{ print $1,$1,$2,$2,$3,$4}` final_chr.${i} > input_${i}
done
and i get
./my_script3.sh: command substitution: line 5: syntax... (2 Replies)
Hi,
I am getting error while running the script. "syntax error: unexpected end of file"
if i do cat i cant see the content of the script also it is showing as
cat test.sh
doner /home/master/* /home/Priya/$i| while read i j
The original script is
paste /home/names.txt /home/ip.txt |... (6 Replies)
I checked the forum and internet, tried different workaorunds but it didnt fixed the error.
Please advise on the code.
#!/bin/sh
CWD=/home/test/Bench
cd $CWD
(grep "`date +%d-%b"`" File.txt) > /home/test/Bench/dateout
if
then
echo “data” > /home/test/ Bench /test
else
echo "File... (16 Replies)
Hi,
I am brand new to this so I apologize ahead of time for any formatting problems.
I know there is a previous (closed) thread on here about this problem but I wasn't able to fix the error following the posts there so I thought I could create a new one.
Here is the error I am getting:
... (3 Replies)
Discussion started by: SierraG
3 Replies
LEARN ABOUT CENTOS
getoptcvt
getoptcvt(1) User Commands getoptcvt(1)NAME
getoptcvt - convert to getopts to parse command options
SYNOPSIS
/usr/lib/getoptcvt [-b] filename
/usr/lib/getoptcvt
DESCRIPTION
/usr/lib/getoptcvt reads the shell script in filename, converts it to use getopts instead of getopt, and writes the results on the standard
output.
getopts is a built-in Bourne shell command used to parse positional parameters and to check for valid options. See sh(1). It supports all
applicable rules of the command syntax standard (see Rules 3-10, intro(1)). It should be used in place of the getopt command. (See the
NOTES section below.) The syntax for the shell's built-in getopts command is:
getopts optstring name [ argument...]
optstring must contain the option letters the command using getopts will recognize; if a letter is followed by a colon (:), the option is
expected to have an argument, or group of arguments, which must be separated from it by white space.
Each time it is invoked, getopts places the next option in the shell variable name and the index of the next argument to be processed in
the shell variable OPTIND. Whenever the shell or a shell script is invoked, OPTIND is initialized to 1.
When an option requires an option-argument, getopts places it in the shell variable OPTARG.
If an illegal option is encountered, ? will be placed in name.
When the end of options is encountered, getopts exits with a non-zero exit status. The special option -- may be used to delimit the end of
the options.
By default, getopts parses the positional parameters. If extra arguments (argument ...) are given on the getopts command line, getopts
parses them instead.
So that all new commands will adhere to the command syntax standard described in intro(1), they should use getopts or getopt to parse posi-
tional parameters and check for options that are valid for that command (see the NOTES section below).
OPTIONS
The following option is supported:
-b Makes the converted script portable to earlier releases of the UNIX system. /usr/lib/getoptcvt modifies the shell script in file-
name so that when the resulting shell script is executed, it determines at run time whether to invoke getopts or getopt.
EXAMPLES
Example 1: Processing the arguments for a command
The following fragment of a shell program shows how one might process the arguments for a command that can take the options -a or -b, as
well as the option -o, which requires an option-argument:
while getopts abo: c
do
case $c in
a | b) FLAG=$c;;
o) OARG=$OPTARG;;
?) echo $USAGE
exit 2;;
esac
done
shift `expr $OPTIND - 1`
Example 2: Equivalent code expressions
This code accepts any of the following as equivalent:
cmd -a -b -o "xxx z yy" filename
cmd -a -b -o "xxx z yy" -filename
cmd -ab -o xxx,z,yy filename
cmd -ab -o "xxx z yy" filename
cmd -o xxx,z,yy b a filename
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of getopts: LC_CTYPE, LC_MESSAGES, and
NLSPATH.
OPTIND This variable is used by getoptcvt as the index of the next argument to be processed.
OPTARG This variable is used by getoptcvt to store the argument if an option is using arguments.
EXIT STATUS
The following exit values are returned:
0 An option, specified or unspecified by optstring, was found.
>0 The end of options was encountered or an error occurred.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|CSI |enabled |
+-----------------------------+-----------------------------+
SEE ALSO intro(1), getopts(1), sh(1), shell_builtins(1), getopt(3C), attributes(5)DIAGNOSTICS
getopts prints an error message on the standard error when it encounters an option letter not included in optstring.
NOTES
Although the following command syntax rule (see intro(1)) relaxations are permitted under the current implementation, they should not be
used because they may not be supported in future releases of the system. As in the EXAMPLES section above, -a and -b are options, and the
option -o requires an option-argument. The following example violates Rule 5: options with option-arguments must not be grouped with
other options:
example% cmd -aboxxx filename
The following example violates Rule 6: there must be white space after an option that takes an option-argument:
example% cmd -ab oxxx filename
Changing the value of the shell variable OPTIND or parsing different sets of arguments may lead to unexpected results.
SunOS 5.10 7 Jan 2000 getoptcvt(1)