05-05-2009
d3vvnull im new to shell scripting so I am sure that there are some flaws in my code. what i want the code to do is check if any of the three values (umts, aws, mmds) exist then echo contine. what could be a better way to do it. and what am i doing wrong
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi Friends,
Is it possible to exit nicely(ie, to echo a message with the error occurred) from a shell script(quiet a big one :)) once it encounter an error in between the lines?
For example, in my script I am calling the command mkdir and sometimes (when the directory already exists) it... (4 Replies)
Discussion started by: Sreejith_VK
4 Replies
2. Shell Programming and Scripting
there are many script in my project.i am having a problem when i am trying to quit from child script.what is the command to wrap up all the parent script and calling script as well? exit 0 is not working.please help.... (1 Reply)
Discussion started by: arghya_owen
1 Replies
3. Shell Programming and Scripting
Hi Folks.
My script is not exiting after run though its working correctly please suggest.
#!/bin/ksh
trap '' HUP
. /bin/functions
config_env
PATH=/bin:/usr/bin:/usr/local/bin:$EXEC_PATH:$ORACLE_HOME/bin
MONTH=$(control_register month)
YEAR=$(control_register year)
DATE_NOW="Job... (1 Reply)
Discussion started by: Haque123
1 Replies
4. Shell Programming and Scripting
Hi,
I am trying to exit the script from a function.
I was in assumption that if we use exit ( inside or outside the function) it will exit from the script.
alternatively, return will exit from that particular function.
but in my case, exit is exiting from the function and not the script.... (8 Replies)
Discussion started by: shellwell
8 Replies
5. Shell Programming and Scripting
I have a script planned for the Helpdesk to allow them to (on a couple of RHEL 3 / RHEL 5 servers) reset passwords, stop / start printers, and clear print queues. The appropriate sudo permissions were given to their accounts, and the individual functions all work just fine. The ability to move... (0 Replies)
Discussion started by: tearsong
0 Replies
6. Shell Programming and Scripting
I have to write a script in ksh which again should call another script. Say A.ksh is calling B.ksh. Now in B.ksh if the condition we are checking for is true then we have to go back to the main script A.ksh or if the condition in B.ksh is false then we have to totally come out of the scripts.
I... (1 Reply)
Discussion started by: vpv0002
1 Replies
7. Shell Programming and Scripting
This is what I've tried:
#!/bin/sh
send sh
send showifs
send exit
! killall minicom
My problem is that for some reason when I do this it doesn't give me the results of the prior commands sent like showifs
So I suspect my syntax is wrong. (1 Reply)
Discussion started by: uradunce
1 Replies
8. Shell Programming and Scripting
Below is the script that i'm using but i'm getting an error,
echo -n "Read the letter >(enter a or b or c) "
read letter
if || || ;
then
echo "unacceptable character"
else
echo "Character Accepted"
fi
if the character entered is not equal to a or b or c, the script should... (6 Replies)
Discussion started by: web2moha
6 Replies
9. Shell Programming and Scripting
Hi Team,
Need your help for the below code snippet. I wrote a module to read the file names remote server using file name convention.
Issue : My script is coming out from while loop without reading complete file.
test1()
{
while read line
do
echo $line
file_nm_convention=`echo... (3 Replies)
Discussion started by: gvkumar25
3 Replies
10. Shell Programming and Scripting
function2()
{
cmd1
cmd2
cmd3
....
cmdn
}
function2()
{
cmd11
cmd12
cmd13
....
....
}
for i in {1,2} (7 Replies)
Discussion started by: yanglei_fage
7 Replies
GETOPT(1) BSD General Commands Manual GETOPT(1)
NAME
getopt -- parse command options
SYNOPSIS
args=`getopt optstring $*` ; errcode=$?; set -- $args
DESCRIPTION
The getopt utility is used to break up options in command lines for easy parsing by shell procedures, and to check for legal options.
Optstring is a string of recognized option letters (see getopt(3)); if a letter is followed by a colon, the option is expected to have an
argument which may or may not be separated from it by white space. The special option '--' is used to delimit the end of the options. The
getopt utility will place '--' in the arguments at the end of the options, or recognize it if used explicitly. The shell arguments ($1 $2
...) are reset so that each option is preceded by a '-' and in its own shell argument; each option argument is also in its own shell argu-
ment.
EXAMPLES
The following code fragment shows how one might process the arguments for a command that can take the options -a and -b, and the option -o,
which requires an argument.
args=`getopt abo: $*`
# you should not use `getopt abo: "$@"` since that would parse
# the arguments differently from what the set command below does.
if [ $? != 0 ]
then
echo 'Usage: ...'
exit 2
fi
set -- $args
# You cannot use the set command with a backquoted getopt directly,
# since the exit code from getopt would be shadowed by those of set,
# which is zero by definition.
for i
do
case "$i"
in
-a|-b)
echo flag $i set; sflags="${i#-}$sflags";
shift;;
-o)
echo oarg is "'"$2"'"; oarg="$2"; shift;
shift;;
--)
shift; break;;
esac
done
echo single-char flags: "'"$sflags"'"
echo oarg is "'"$oarg"'"
This code will accept any of the following as equivalent:
cmd -aoarg file file
cmd -a -o arg file file
cmd -oarg -a file file
cmd -a -oarg -- file file
SEE ALSO
sh(1), getopt(3)
DIAGNOSTICS
The getopt utility prints an error message on the standard error output and exits with status > 0 when it encounters an option letter not
included in optstring.
HISTORY
Written by Henry Spencer, working from a Bell Labs manual page. Behavior believed identical to the Bell version. Example changed in FreeBSD
version 3.2 and 4.0.
BUGS
Whatever getopt(3) has.
Arguments containing white space or embedded shell metacharacters generally will not survive intact; this looks easy to fix but isn't. Peo-
ple trying to fix getopt or the example in this manpage should check the history of this file in FreeBSD.
The error message for an invalid option is identified as coming from getopt rather than from the shell procedure containing the invocation of
getopt; this again is hard to fix.
The precise best way to use the set command to set the arguments without disrupting the value(s) of shell options varies from one shell ver-
sion to another.
Each shellscript has to carry complex code to parse arguments halfway correcty (like the example presented here). A better getopt-like tool
would move much of the complexity into the tool and keep the client shell scripts simpler.
BSD
April 3, 1999 BSD