04-20-2013
I don't understand how you got the idea that 'continue' and 'break' are somehow tied to user input. They are for flow control and are used whenever a program needs to exit a loop or skip the rest of the current iteration. You will find these types of statements in programs that do not even have a controlling terminal, much less interact with a user.
For reading user input, assuming it's on stdin, some awk's support /dev/stdin. You can use that with getline.
Regards,
Alister
Last edited by alister; 04-20-2013 at 01:34 PM..
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
CO UNixware 7.1.1
Hi friends,
I have chopped my case statementt out of my .profile and put it in another script called setsid. The case statement works when run from my .profile but not from my setsid file.
All that the script does is set an environmental variable based on user input.... (7 Replies)
Discussion started by: sureshy
7 Replies
2. Shell Programming and Scripting
Hi -
Trying to take a list of ldap suffixes in a file, run an ldapsearch command on them, then run a grep command to see if it's a match, if not, then flag that and send an email alert.
The list file (ldaplist) would look like -
***********
o=company a
o=company b
***********
**... (7 Replies)
Discussion started by: littlefrog
7 Replies
3. Shell Programming and Scripting
Always, I have a confuse/not understand file descriptors.
I know about the
0 for standard input
1 for standard output
2 for standard error
and 3 to 9 is a additional file descriptor but it's a theoritical knowledge.
Could you please give information about below two lines of code in AIX... (1 Reply)
Discussion started by: div_Neev
1 Replies
4. AIX
Hello,
after upgrading the memory to 96GB & 6 Dual Processor for P 550 ( and still not applied the parameters which some experienced posters said in post https://www.unix.com/aix/141835-oracle-database-running-slow-aix-nmon-topas-6.html )
I am getting system dumps. How to understand and... (1 Reply)
Discussion started by: filosophizer
1 Replies
5. Shell Programming and Scripting
I have the following and for some reason I can't have two options together.
I mean if I choose -u and -p it won't work... why?
#!/bin/bash
resetTime=1
mytotalTime=0
totalHour=0
totalMin=0
averagemem=0
finalaverage=0
times=0
function usage()
{
cat << EOF
USAGE: $0 file
EOF
} (10 Replies)
Discussion started by: bashily
10 Replies
6. UNIX for Dummies Questions & Answers
Can some one please help me know how exactly to understand logs in sendmail 8.14.5. I am pretty new to sendmail.
I am running rhel6 on my system and i installed sendmail on it. Its just a test enivornment and i am sending and receiving emails on my localshot only.
Jun 13 18:32:38 serv1... (0 Replies)
Discussion started by: Rohit Bhanot
0 Replies
7. Red Hat
I ran the following grep and sed command.
grep "\t" emp.txt
sed -n '/\t/p' emp.txt
grep treated the '\' as to escape t and took the pattern as literal t whereas sed took the pattern as tab.
That means , grep doesn't understand escape sequence!!!!!!
what to do to make grep... (8 Replies)
Discussion started by: ravisingh
8 Replies
8. Shell Programming and Scripting
greetings,
the following code isn't working as i expect it to. the first dbl brackets do but the second set gets ignored. ie: if i'm on t70c6n229 it echoes "Something" and i expect it not to. what am i missing?
if " ]] || " ]]; then
echo "Something"
fi
thanx! (9 Replies)
Discussion started by: crimso
9 Replies
9. Shell Programming and Scripting
I Bourne shell I have a lines
#!/bin/sh
something
for file in *_${Today}*.csv *_${Today}*.txt
do
if
then
echo "This file will be processed in separate script"
continue
fi
something
done
The script doesn't understand if... (6 Replies)
Discussion started by: digioleg54
6 Replies
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]
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 man 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 vari-
able assignment. This means that tilde substitution is performed after the = sign, and also that word splitting and file name genera-
tion 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), sh( 1), attributes(5)
SunOS 5.10 17 Jul 2002 break(1)