Looking for a command that is just like the goto but for os x bash

Bone11409 · 11-07-2009, 02:14 AM

Hey I need a command like goto but for the os x leopard using bash I have look on the net but have not found any thing.

druuna · 11-07-2009, 04:32 AM

Hi,

Bash does not have a goto statement.

Depending on what you want to do, which you do not mention, you need to use some other construction.

Post the problem (as detailed as possible) and we are probably able to help you with a solution.

Hope this helps.

Bone11409 · 11-07-2009, 10:32 AM

Ok I am trying to compare this variable gateway=$(netstat -r | grep default | awk '{print $2}' to a list of 5 different gateway address's and then when it cycles threw and finds the one it match's to then it will skip the comparing of the rest and give me another variable to show that gateway's name. Here's kind of what I had in mind.

#!/bin/bash
gateway=$(netstat -r | grep default | awk '{print $2}'
if [ "$gateway" = "10.184.16.1"]; then
name=$1floor
goto line1
else
if [ "$gateway" = "10.184.32.1"]; then
name=$2floor
goto line1
else
line1
exit
fi
fi
'

catkin · 11-07-2009, 10:54 AM

Code:

#!/bin/bash
gateway=$(netstat -r | grep default | awk '{print $2}'
case "$gateway" in
    '10.184.16.1' )
        name=${1}floor
        ;;
    '10.184.32.1' )
        name=${2}floor
        ;;
    * )
        <error commands>
esac

<line1 commands>
exit

Bone11409 · 11-07-2009, 11:20 AM

Hey I just try your script here on my laptop and it did not work for me. Also could you walk me threw that command I have not seen it before.

command substitution: line 6: syntax error near unexpected token `newline'
/Users/bone/Desktop/fixodtest: command substitution: line 6: ` '10.184.16.1' '
/Users/bone/Desktop/fixodtest: line 6: syntax error near unexpected token `;;'
/Users/bone/Desktop/fixodtest: line 6: ` ;;'

catkin · 11-07-2009, 11:43 AM

Quote:

Originally Posted by Bone11409

Hey I just try your script here on my laptop and it did not work for me. Also could you walk me threw that command I have not seen it before.

command substitution: line 6: syntax error near unexpected token `newline'
/Users/bone/Desktop/fixodtest: command substitution: line 6: ` '10.184.16.1' '
/Users/bone/Desktop/fixodtest: line 6: syntax error near unexpected token `;;'
/Users/bone/Desktop/fixodtest: line 6: ` ;;'

The GNU Bash Reference Manual and Advanced Bash-Scripting Guide describe the case-esac command.

As a matter of good practice I changed the double quotes around the IP addresses to single quotes (it would have worked with the double quotes but it is prudent to use single quotes unless double quotes are necessary).

I changed $1floor to ${1}floor presuming you wanted the value of $1 suffixed with the string 'floor' -- the original usage would have referenced a variable named 1floor.

Regards your error, try changing

Code:

gateway=$(netstat -r | grep default | awk '{print $2}'

to

Code:

gateway="$(netstat -r | grep default | awk '{print $2})')"

Sorry -- I did not notice the missing ')' in your original post. Adding the double quotes is good practice in case the string returned by the netstat command has embedded whitespace; without the double quotes bash would try to run anything after the whitespace as a command.

Bone11409 · 11-07-2009, 05:55 PM

Here's what I have come up with it's simple and it work's

#!/bin/bash
gateway=$(netstat -r | grep default | awk '{print $2}')
if [ "$gateway" = "10.184.16.1" ]; then
name=$"1floor"
fi
if [ "$gateway" = "10.184.32.1" ]; then
name=$"2floor"
fi
echo "$name"

catkin · 11-08-2009, 01:33 AM

Quote:

Originally Posted by Bone11409

Here's what I have come up with it's simple and it work's

#!/bin/bash
gateway=$(netstat -r | grep default | awk '{print $2}')
if [ "$gateway" = "10.184.16.1" ]; then
name=$"1floor"
fi
if [ "$gateway" = "10.184.32.1" ]; then
name=$"2floor"
fi
echo "$name"

Glad it works for you. Why are you using ANSI-C quoted strings in name=$"1floor" when you have no backslash-escape sequences rather than the simpler name=1floor?

Bone11409 · 11-08-2009, 11:15 AM

No reason just over looked it