ok, ive done a bit of digging and it seems "continue" is the command im after to drop me out of the loop. However, the strangest thing has come to light....If i put my "continue" statement within my "if" statement within my "for" loop, then everything works as expected by throwing me out when there is a failure on the first "if" statement.... like this
Code:
#!/bin/ksh
for n in list
do
# what was function1
ping $n 2 > /dev/null
if [ $? != 0 ] ; then
echo "Couldn't ping $n, skipping"
continue
else
echo "ping to $n successful, continuing to function2"
fi
# what was function2
location=`ssh $1 'cat /etc/location'`
if [ $location = "London" ] ; then
loc=ldn
echo "Location is London, passing on to function3"
else
echo "location is NOT London, Skipping"
continue
fi
done
Now that is exactly what I want, apart from the fact I have had to put what were externally defined functions, physically within the for loop.
If i define them outside of the for loop and call them in, the continue statement is ignored
so the following code doesnt work
Code:
#!/bin/ksh
# ************* FUNCTIONS ******************
function1() { #ping test
ping $1 2 > /dev/null
if [ $? != 0 ] ; then
echo "Couldn't ping $1, skipping"
continue
else
echo "ping to $1 successful, continuing to function2"
fi
}
function2() { # now we can ping ...check the location
location=`ssh $1 'cat /etc/location'`
if [ $location = "London" ] ; then
loc=ldn
echo "Location is London, passing on to function3"
else
echo "location is NOT London, Skipping"
continue
fi
}
#### main script body ####
for n in list
do
function1 $n
function2 $n
done
I just dont understand why it works if i embed the code, but it doesnt if I define it as a function and call it in - what is the difference, arent functions treated as embedded code when they are called in ?????
I really would prefer to keep this function based as the code is a lot tidier
Is anybody able to explain to me why this happens....im stumped
I am running an Ubuntu Gutsy laptop with Advanced Compiz fusion options enabled. I am using xdotool to simulate keyboard input in order to rotate through multiple desktops.
I am looking for a way to kill a while true loop when the Enter key (or Control+C if it is easier) is pushed when the... (2 Replies)
All,
I'm having a problem w/this function. Specifically, I want to call another function (get_stats) when the process in the else completes (the initial if and the elsif seem to work fine). But what's happening is the get_stats function call is running after the else runs only once, NOT when it... (8 Replies)
Greeting,
The following script completes after reading only one record from the input file that contains many records. I commented out the "ssh" and get what I expect, an echo of all the records in the input.txt file. Is ssh killing the file handle?
On the box "uname -a" gives "SunOS... (2 Replies)
Hi my code looks like:
if test $STEP -le 10
then
.
.
ls -1d AM*-OUT|while read MYDIR
do
cd $MYDIR
ls |tail -n1| while read MYFILE
do
.
.
if test -s $MYFILE
then
sqlldr ....
rc=$?
if test $rc -ne 0 (3 Replies)
Hi,
I have a really simple script which I want to run forever, inside the loop it runs a C application which if it exits should restart.
#!/bin/sh
while true
do
./SCF scf.conf >> scf.log
sleep 2
done
For some reason the SCF C application coredumps and the script is exiting.... (3 Replies)
Hi I am having a problem exiting a WHILE loop. I am on a Sun server using ksh.
I am running a Veritas Cluster Software (High Availablity) command to obtain a group status and grepping the command output for status "G" which means that the filesystem is frozen and therefore not available to... (3 Replies)
Hello all,
I have a problem when installing Solaris 10 on Enterprise 450.
I booted from dvd, then the installation was started. The error appeared after determining the installation method, F2-Standard, F?-Flash......
The error was Exiting signal 6.
Please, need help. Thank you (4 Replies)
We are trying to design a flow so that an ETL job shouldn't start until the previous job completes. The script we have written is
while ; do sleep 2; done
The loop however exits even when the process is actually running. Why could this be happening? (12 Replies)
Hi ,
I am processing some files using below shell script the problem for loop exit after processing some files even though it exist.After modifying file.txt and rerunning the script and its running .Any Advise
for i in `cat /xx/file.txt |tr -s "," '\n' ` ; do
echo $i... (3 Replies)
Discussion started by: mohan705
3 Replies
LEARN ABOUT OPENSOLARIS
break
break(1) User Commands break(1)NAME
break, continue - shell built-in functions to escape from or advance within a controlling while, for, foreach, or until loop
SYNOPSIS
sh
break [n]
continue [n]
csh
break
continue
ksh
*break [n]
*continue [n]
ksh93
+break [n]
+continue [n]
DESCRIPTION
sh
The break utility exits from the enclosing for or while loop, if any. If n is specified, break n levels.
The continue utility resumes the next iteration of the enclosing for or while loop. If n is specified, resume at the n-th enclosing loop.
csh
The break utility resumes execution after the end of the nearest enclosing foreach or while loop. The remaining commands on the current
line are executed. This allows multilevel breaks to be written as a list of break commands, all on one line.
The continue utility continues execution of the next iteration of the nearest enclosing while or foreach loop.
ksh
The break utility exits from the enclosed for, while, until, or select loop, if any. If n is specified, then break n levels. If n is
greater than the number of enclosing loops, the outermost enclosing loop shall be exited.
The continue utility resumes the next iteration of the enclosed for, while, until, or select loop. If n is specified then resume at the n-
th enclosed loop. If n is greater than the number of enclosing loops, the outermost enclosing loop shall be used.
On this manual page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words that follow a command preceded by ** that are in the format of a variable assignment are expanded with the same rules as a
variable assignment. This means that tilde substitution is performed after the = sign, and also that word splitting and file
name generation are not performed.
ksh93
break is a shell special built-in that exits the smallest enclosing for, select, while, or until loop. It also exits the nth enclosing loop
if n is specified. Execution continues at the command following the loop or loops.
If n is specified, it must be a positive integer >=1. If n is larger than the number of enclosing loops, the last enclosing loop is exited.
continue is a shell special built-in that continues execution at the top of the smallest enclosing for, select, while, or until loop, if
any; or of the top of the nth enclosing loop if n is specified.
If n is specified, it must be a positive integer >=1. If n is larger than the number of enclosing loops, the last enclosing loop is used.
On this manual page, ksh93(1) commands that are preceded by one or two + symbols are special built-in commands and are treated the follow-
ing ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Built-in commands are not valid function names.
5. Words following a command preceded by ++ that are in the format of a variable assignment are expanded with rules as a variable
assignment. This means that tilde substitution is performed after the = sign and field splitting and file name generation are
not performed.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO csh(1), exit(1), ksh(1), ksh93(1), sh(1), attributes(5)SunOS 5.11 8 Apr 2008 break(1)
11-26-2008
