Else Loop Exiting Early Post: 302177256

Sponsored Content

Top Forums Shell Programming and Scripting Else Loop Exiting Early Post 302177256 by joeyg on Thursday 20th of March 2008 12:59:07 PM

03-20-2008

Registered User

Clarifications..

1) Correct. I want it to run until 8675309 starts. Then on the next check it should go to else.

2) Should I change it to
if [ $UL_FILE_TYPE = TEMP -a $UL_PROCESS -eq 0 ]
That is check the file type first and then check for the process?

3) elif is correct; my misspelling. Thanks for the catch!

In response:
1) I think this is odd as you will have two occurrences of the program then running. You run, catch the condition, wait, and start again "as a sub-process". This 2nd run may have different results at "if" statements. Assuming it too does not get caught by the first loop - thus creating a third instance of the script running - control would be returned to the first run at the "elsif" line. Perhaps rethink the logic to a "do while" or "do until" set of commands?
2) I was not commenting on the order within the if, more the logic that I do not believe the program could ever find your "elsif" logic true and able to be executed. The first if is true (UL -eq 0) meaning the "elsif" would not be exexcuted. The first is false (UL -eq 0) meaning the "elsif" would be analyzed, but how could it be now true? Unless this is all to catch the sub-process I referred to in (1)?
3) Concur that "elsif" should be "elif". My other point is that an "elif" should then have its own "then". "elif" expects a "then", so does the program skip a bunch of logic until it finds your next "then" occurrence?

joeyg

View Public Profile for joeyg

Find all posts by joeyg

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Bash: Exiting while true loop when terminal is not the focus window

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. Shell Programming and Scripting

exiting from a loop

I wonder if someone could help me here. I am trying to find a way of exiting from a loop but not exiting me from the script for example #!/bin/ksh # ************* FUNCTIONS ****************** function1() { #ping test ping $1 2 > /dev/null if ; then ...

3. UNIX Benchmarks

Early PowerMac G5

Hardware Overview: Model Name: Power Mac G5 Model Identifier: PowerMac7,2 Processor Name: PowerPC 970 (2.2) Processor Speed: 1.8 GHz Number Of CPUs: 2 L2 Cache (per CPU): 512 KB Memory: 1.5 GB Bus Speed: 900 MHz Boot ROM Version:...

4. UNIX for Advanced & Expert Users

"while read ..." loop exiting after reading only one record

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...

5. Shell Programming and Scripting

Problem in exiting a loop

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

6. Shell Programming and Scripting

Loop Forever Script Strangely Exiting

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....

7. Shell Programming and Scripting

Problem exiting a WHILE loop in ksh

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...

8. Shell Programming and Scripting

While Loop Exiting

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?

9. Shell Programming and Scripting

For loop exiting

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...

LEARN ABOUT REDHAT

xmlif

XMLIF(1)																  XMLIF(1)

NAME

       xmlif - conditional processing instructions for XML

SYNOPSIS

       xmlif [attrib=value...]

DESCRIPTION

       xmlif  filters  XML  according  to  conditionalizing  markup.  This can be useful for formatting one of several versions of an XML document
       depending on conditions passed to the command.

       Attribute/value pairs from the command line are matched against the attributes associated with certain processing instructions in the docu-
       ment. The instructions are <?if> and its inverse <?if not>, <?elif> and its inverse <?elif not>, <?else>, and <?fi>.

       Argument/value  pairs  given  on  the  command line are checked against the value of corresponding attributes in the conditional processing
       instructions. An `attribute match' happens if an attribute occurs in both the command-line arguments and the tag, and the values match.	An
       `attribute mismatch' happens if an attribute occurs in both the command-line arguments and the tag, but the values do not match.

       Spans  between  <?if>  or <?elif> and the next conditional processing instruction at the same nesting level are passed through unaltered if
       there is at least one attribute match and no attribute mismatch; spans between <?if not> and <?elif not> and the next conditional  process-
       ing  instruction are passed otherwise. Spans between <?else> and the next conditional-processing tag are passed through only if no previous
       span at the same level has been passed through. <?if> and <?fi> (and their `not' variants) change the current nesting  level;  <?else>  and
       <?elif> do not.

       All  these  processing  instructions will be removed from the output produced. Aside from the conditionalization, all other input is passed
       through untouched; in particular, entity references are not resolved.

       Value matching is by string equality, except that "|" in an attribute value is  interpreted  as	an  alternation  character.  Thus,  saying
       foo='red|blue'  on  the	command  line enables conditions red and blue. Saying color='black|white' in a tag matches command-line conditions
       color='black' and color='white'.

       Here is an example:

       Always issue this text.
       <?if condition='html'>
       Issue this text if 'condition=html' is given on the command line.
       <?elif condition='pdf|ps'>
       Issue this text if 'condition=pdf' or 'condition=ps'
       is given on the command line.
       <?else>
       Otherwise issue this text.
       <?fi>
       Always issue this text.

FUTURE DIRECTIONS

       The mark-up used by this tool is not set in stone, and may change in the near future.

AUTHOR

       Eric S. Raymond.

								    Sep 26 2002 							  XMLIF(1)