Sponsored Content
Homework and Emergencies Homework & Coursework Questions Syntax error near unexpected token 'else' Post 302548276 by Ren_kun on Thursday 18th of August 2011 02:48:07 AM
Old 08-18-2011
Question Syntax error near unexpected token 'else'

1. The problem statement, all variables and given/known data:

line 37: syntax error near unexpected token 'else'
line 37: ' else'

the script is made to take 1 or 2 command line arguments however i get the above stated error when trying to process it. This happens with or without arguments inputted. I looked over and over it however i cant see why the else is giving an error, i have an even amount of if - fi 's and the else is placed within the if - fi code. Im not sure what im doing wrong. Thanks in advance.

2. Relevant commands, code, scripts, algorithms:

P.S. I am using cygwin in windows to do this script.

3. The attempts at a solution (include all code and scripts):
Image

4. Insearch: (University of Technology Sydney), Sydney NSW, Australia, James Hu (web systems), www(dot)insearch.edu.au/default.aspx?ArticleID=430

Note: Without school/professor/course information, you will be banned if you post here! You must complete the entire template (not just parts of it).

Last edited by Ren_kun; 08-18-2011 at 03:58 AM..
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

sh syntax error unexpected token done

I'm getting the following error: line 21: syntax error near unexpected token `done` line 21: `done` and I haven't been able to figure out why. Here is my code #!/bin/sh if ; then echo 'Usage: rename getexp/replStr ' exit 0 fi arg = $1 shift while ; do (5 Replies)
Discussion started by: NullPointer
5 Replies

2. UNIX for Advanced & Expert Users

syntax error near unexpected token '{

Hi, I am running the following script through cygwin and getting below mentioned error. ******************************************* #!/bin/sh # constants WORK_DIR="deploy" INFOFILE="deploy.info" INTROFILE="Intro.sh" CMGMT_PKG="com.kintana.cmgmt.deploy" DEPLOY_PREFIX="mitg" ... (2 Replies)
Discussion started by: MandyR
2 Replies

3. Shell Programming and Scripting

syntax error near unexpected token `='

Hi all, This is a script which converts hex to bin. However am finding an error while executing syntax error near unexpected token `=' `($hexfile, $binfile) = @ARGV;' I am running using ./fil.pl <hexfile> <binfile> ################################################### # # this script... (3 Replies)
Discussion started by: jaango123
3 Replies

4. Shell Programming and Scripting

Syntax error near unexpected token `('

What do I do here? #!/bin/bash payload=-1 AND 1=IF(21,BENCHMARK(5000000,MD5(CHAR(115,113,108,109,97,112))),0)# hash=`echo -n $payload md5sum tr -d 'n' sed 'ss-sg' md5sum tr -d 'n' sed 'ss-sg'` curl --data cs2=chronopay&cs1=$payload&cs3=$hash&transaction_type=rebill... (2 Replies)
Discussion started by: iiiiiiiiiii
2 Replies

5. Shell Programming and Scripting

Syntax error near unexpected token `else'

Hi, I am trying to read the session log through script. But it keeps showing me some error near. I have tried everything. Even tried converting the script using sed command to remove the hidden characters(\r).But nothing seems to be working.Below is the script : #!/bin/bash cd... (6 Replies)
Discussion started by: Aryan12345
6 Replies

6. Shell Programming and Scripting

Syntax error near unexpected token '('

I tried to execute the code but I got this error ./Array.c: line 9: syntax error near unexpected token '(' ./Array.c: line 9: ' nvals = get_data(a,MAXARRAY);' and #include<stdio.h> #define MAXARRAY 1000 main() { int a, nvals; nvals =... (7 Replies)
Discussion started by: sgradywhite
7 Replies

7. Shell Programming and Scripting

Syntax error near unexpected token

Hi all, I have a simple script that doesn't work somehow. I can't seem to be spotting the cause of the malfunction. count=$((1)) for item in `cat test1.txt` printf %s `sed -n $((count))p test2.txt` > test3.txt count=$((count+1)) do something done I get ; ./why.sh: line 3:... (14 Replies)
Discussion started by: y33t
14 Replies

8. How to Post in the The UNIX and Linux Forums

Syntax error near unexpected token `('

I have 2 files like a.txt and b.txt and the content is as below cat a.txt 810750125 117780 /BSCSQAT4A/bscsqat4a/lib/jar/wclt_common.jar 1803152428 13300 /BSCSQAT4A/bscsqat4a/lib/jar/WFMSSupportTool.jar 2663502779 67049 /BSCSQAT4A/bscsqat4a/lib/jar/wma.jar 687942896 665272... (1 Reply)
Discussion started by: ranabhavish
1 Replies

9. UNIX for Beginners Questions & Answers

Syntax error near unexpected token

Dears, While executing the below script im getting the error at line 30. Please let me know what changes to be done to fix this. test.sh: line 30: syntax error near unexpected token `done' test.sh: line 30: ` done ' #!/bin/sh # Rev. PA1 # author: eillops # date: 26-04-2018 # #... (1 Reply)
Discussion started by: Kamesh G
1 Replies

10. Ubuntu

Syntax error near unexpected token `('

detect_mouse_mvt.sh /home/andy/bin/detect_mouse_mvt.sh: line 4: syntax error near unexpected token `(' /home/andy/bin/detect_mouse_mvt.sh: line 4: `fh = file('/dev/input/mice')' #!/bin/bash # # fh = file('/dev/input/mice') while True: fh.read(3) print 'Mouse... (15 Replies)
Discussion started by: drew77
15 Replies
getsubopt(3)						     Library Functions Manual						      getsubopt(3)

NAME
getsubopt - Parses suboption arguments from a command line LIBRARY
Standard C Library (libc.so, libc.a) SYNOPSIS
#include <stdlib.h> int getsubopt( char **optionp, char *tokens[], char **valuep); STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: getsubopt(): XPG4-UNIX Refer to the standards(5) reference page for more information about industry standards and associated tags. PARAMETERS
Specifies the address of a pointer to the option string. Specifies an array of possible suboption tokens. Specifies the address of a value string pointer. DESCRIPTION
The getsubopt() function parses suboption arguments in a flag argument that was initially parsed by the getopt() function. These suboption arguments must be separated by commas and may consist of either a single token, or a token-value pair separated by an equal sign. Because commas delimit suboption arguments in the option string, commas are not allowed to be part of the suboption arguments or the value of a suboption argument. Similarly, because the equal sign separates a token from its value, a token must not contain an equal sign. The following command line for the mount command gives an example of this syntax: mount -o ro,nosuid,rsize=8192 paradox:/u2 /u2 In this example, the suboption consists of three arguments: ro and nosuid (tokens), and rsize=8192 (a token-value pair). When a suboption argument is found in the *optionp string that matches a string in the token array, the index of the matching string in the array is returned. If no match is found, then a -1 is returned. After each match, the *optionp string is updated to point past the matched suboption argument to the next suboption argument in the list. If the suboption argument matched is the last in the string, *optionp is set to the null pointer. If the suboption argument matched is a token-value pair, then *valuep is set to point to the value. If there is no value, then *valuep is to the null pointer. The token array is a list of pointers to strings. The end of the array is signified by a NULL pointer. RETURN VALUES
Upon successful completion, the getsubopt() function returns the index of the token or suboption argument that matches the suboption argu- ment in the input string. Otherwise, if no match is found, it returns a value of -1. ERRORS
No errors are defined for this routine. RELATED INFORMATION
Functions: getopt(3) Standards: standards(5) delim off getsubopt(3)
All times are GMT -4. The time now is 04:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy