03-20-2008
while do loop
I would think your first choice easier to understand and error-check.
I personally like the first approach since between those two lines you can insert
>echo $UL_PROCESS
This get to preference, skill level, speed necessary (if churning thru lots of records) and ability for others to understand your code in the future. Thus, I normally choose the path where I set a variable in one line, then check it next.
Perhaps logic like the following, and I know the syntax is all bad!
while $UL -eq 0
do
if filetype=temp
then
do your hostname thing
exit
fi
sleep
date # show that something is happening and looping, delete later
done
#at this point $UL -ne 0 & not temp filetype
#so the rest of your logic
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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)
Discussion started by: acclaypool
2 Replies
2. Shell Programming and Scripting
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
... (13 Replies)
Discussion started by: hcclnoodles
13 Replies
3. UNIX Benchmarks
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:... (0 Replies)
Discussion started by: tnorth
0 Replies
4. UNIX for Advanced & Expert Users
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)
Discussion started by: twk
2 Replies
5. Shell Programming and Scripting
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)
Discussion started by: anijan
3 Replies
6. Shell Programming and Scripting
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)
Discussion started by: marvinwright
3 Replies
7. Shell Programming and Scripting
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)
Discussion started by: bigbuk
3 Replies
8. Shell Programming and Scripting
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)
Discussion started by: jerome_rajan
12 Replies
9. Shell Programming and Scripting
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 DEBIAN
acheck.1
ACHECK.1(1) User Contributed Perl Documentation ACHECK.1(1)
NAME
acheck - Check common localization mistakes
SYNOPSIS
acheck [OPTIONS] [INPUT_FILE]
DESCRIPTION
This program parses a file checking for syntax rules and optionally asking Aspell for checking word spelling. It makes fix suggestions and
outputs a corrected file accordingly adding review comments if requested.
It tries to find the file type according to the extension or the first lines and loads rules accordingly.
It displays lines when they are parse.
When an error is found, a menu is displayed. Just press Enter if you don't want to change anything. If a choice suits you, enter the corre-
sponding number. If you want to fix it but no choice is correct, enter a space, then you will be asked for a string to replace the high-
lighted text. The script will replace the highlighted text with your choice and parse it again for new errors.
Here are all the available commands:
Enter, ignore.
Ignore.
Ctrl+L, redraw.
Rewrite the last line, suggestions and hints.
Space, edit.
Edit the highlighted text.
E, edit line.
Edit the whole line.
H, add hint.
Add the displayed hint as review comment. Use this if you want the translator to see the corresponding warning or error but you have no
correction.
N, next line.
Skip the rest of this line.
X, exit and discard all changes.
Quit without saving modifications, the script ask you for confirmation, you have to enter `yes' to exit otherwise parsing starts again
at the current mistake.
a, add in dictionary.
Add the highlighted word to you personal dictionary, capitalized as it is.
l, add lowercase in dictionary.
Lowercase the highlighted word to add it to your personal dictionary.
i, ignore word.
Ignore the highlighted word, same as Enter.
I, ignore all.
Ignore the highlighted word and add it to your session dictionary.
OPTIONS
Verbosity level:
-q, --quiet
quiet mode.
-v verbose, start at level $Debug + 1, add more for more verbosity (see below).
--verbose n
set verbosity level to n (see below).
Files:
-i, --input
input filename, can be '-' to read data from standard input.
-o, --output
output filename, can be '-' to write data to standard ouput. If no output filename is provided, input file is backed up with `bak_ext'
extension and input filename is used.
Spell check:
-s, --spell
check spelling with Aspell.
-d language, --dict language
use language dictionary for Aspell.
-n, --nospell
don't check spelling.
Mode:
-r, --review
review mode, add comments on lines beginning with $Comment after parsed line.
-t, --trans
translator mode, don't add comments, just fix errors.
others:
--rules ruleset
use ruleset rules set.
--type filetype
use filetype whatever the file type is.
--dump
Dump the rules to check and exit, use this for debugging purposes.
-V, --version
print version and exit.
-h, --help
print a short usage message and exit.
Verbosity Level
0 quiet, normal
only warnings and errors
1 debug
names of subroutines
2 debug verbose
names and arguments of subroutines
3 .. 5 debug very verbose
output parsing and checking details
SEE ALSO
acheck(5), acheck-rules(5)
AUTHOR
Nicolas Bertolissio <bertol@debian.org>
perl v5.8.4 2003-10-05 ACHECK.1(1)