10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
here is my script that expects the user to run it like
./best.sh -f /tmp/log.txt
more best.sh
#!/bin/bash
while getopts ":f:" opt; do
case $opt in
f) file_in="$OPTARG"
;;
\?) echo "Invalid option -$OPTARG" >&2
;;
esac
done uname -a
SunOS mymac 5.11 11.2 sun4v... (15 Replies)
Discussion started by: mohtashims
15 Replies
2. Shell Programming and Scripting
Hi All,
I am writing a script to pass the getopts argument to the function which I have. But it as soon as I execute the script, the argument is taking it as blank. I tried using multiple way to check but its not working.
Can someone please let me know what wrong in this code.
function1()... (4 Replies)
Discussion started by: sidh_arth85
4 Replies
3. Shell Programming and Scripting
I'm using getopts to process command line args in a Bash script. The code looks like this:
while getopts ":cfmvhs:t:" option; do
case $option in
c) operationMode="CHECK"
;;
f) operationMode="FAST"
;;
m) ... (6 Replies)
Discussion started by: gencon
6 Replies
4. Shell Programming and Scripting
How can I say one of the options is required? can I use an if statement?
let say:
while getopts ":c:u:fp" opt; do
case $opt in
c) echo "-c was triggered, Parameter: $OPTARG" >&2;;
u) echo "-u was triggered, Parameter: $OPTARG" >&2;;
f) echo "-u was triggered,... (2 Replies)
Discussion started by: bashily
2 Replies
5. Shell Programming and Scripting
i have the following scenario want to run the following script with manadory and optional argumnets
Manadory options are :
filename=""
port=""
optional arguments
type -t
balances -b bal
prices -p
./test filename port -t A -b bal
my code i have that won't parse the options is... (1 Reply)
Discussion started by: nano2
1 Replies
6. UNIX for Dummies Questions & Answers
Hi, I'm having problems with a script where I wanted every single option specified in the command line to have an argument taken with it, but for some reason only d works in the code I will be showing below.
For example if I did ./thisfile -a something
it would come up with "a chosen with " as... (2 Replies)
Discussion started by: IceX
2 Replies
7. HP-UX
Is there a restriction on levels of using 'getopts' ? I have several scripts, each of which requires an option as the first parameter .
If I call one prg separately it works fine, but when one prg calls another prg and passes the option on the called prg, then the called prg
seems not to process... (3 Replies)
Discussion started by: vslewis
3 Replies
8. Shell Programming and Scripting
I need to create a shell script having the menu with few options such as
1. Listing 2. Change permissions 3. Modify Contents 4. Delete Files 5. Exit
1. For 1. Listing: Display a special listing of files showing their date of modification and access time (side by side) along with their... (2 Replies)
Discussion started by: bab123
2 Replies
9. Shell Programming and Scripting
Hi,
My script will take a input file as a parameter(which is not mandatory) and also an option.
ksh my_script.sh <inputfile>
The option -n I have given is no way related to the input file.
Now the problem here is when i execute the script specifying the input file and the option(the way... (4 Replies)
Discussion started by: chella
4 Replies
10. Shell Programming and Scripting
Hi
i have part of the scripts below ,getopt for -h or ? not working for me.
can anybody tell me if this sytax right or wrong.
#!/usr/bin/ksh
program=$(basename $0)
#####################################################################################
function usageerr
{
RC=1
... (3 Replies)
Discussion started by: GrepMe
3 Replies
shell_builtins(1) shell_builtins(1)
NAME
shell_builtins, case, for, foreach, function, if, repeat, select, switch, until, while - shell command interpreter built-in commands
The shell command interpreters csh(1), ksh(1), and sh(1) have special built-in commands. The commands case, for, foreach, function, if,
repeat, select, switch, until, and while are commands in the syntax recognized by the shells. They are described in the Commands section of
the manual pages of the respective shells. The remaining commands listed in the table below are built into the shells for reasons such as
efficiency or data sharing between command invocations. They are described on their respective manual pages.
|
Command | Shell
alias |csh, ksh
bg |csh, ksh, sh
break |csh, ksh, sh
case |csh, ksh, sh
cd |csh, ksh, sh
chdir |csh, sh
continue |csh, ksh, sh
dirs |csh
echo |csh, ksh, sh
eval |csh, ksh, sh
exec |csh, ksh, sh
exit |csh, ksh, sh
export |ksh, sh
false |ksh
fc |ksh
fg |csh, ksh, sh
for |ksh, sh
foreach |csh
function |ksh
getopts |ksh, sh
glob |csh
goto |csh
hash |ksh, sh
hashstat |csh
history |csh
if |csh, ksh, sh
jobs |csh, ksh, sh
kill |csh, ksh, sh
let |ksh
limit |csh
login |csh, ksh, sh
logout |csh, ksh, sh
nice |csh
newgrp |ksh, sh
nohup |csh
notify |csh
onintr |csh
popd |csh
print |ksh
pushd |csh
pwd |ksh, sh
read |ksh, sh
readonly |ksh, sh
rehash |csh
repeat |csh
return |ksh, sh
select |ksh
set |csh, ksh, sh
setenv |csh
shift |csh, ksh, sh
source |csh
stop |csh, ksh, sh
suspend |csh, ksh, sh
switch |csh
test |ksh, sh
time |csh
times |ksh, sh
trap |ksh, sh
true |ksh
type |ksh, sh
typeset |ksh
ulimit |ksh, sh
umask |csh, ksh, sh
unalias |csh, ksh
unhash |csh
unlimit |csh
unset |csh, ksh, sh
unsetenv |csh
until |ksh, sh
wait |csh, ksh, sh
whence |ksh
while |csh, ksh, sh
Bourne Shell, sh, Special Commands
Input/output redirection is now permitted for these commands. File descriptor 1 is the default output location. When Job Control is
enabled, additional Special Commands are added to the shell's environment.
In addition to these built-in reserved command words, sh also uses:
: No effect; the command does nothing. A zero exit code is returned.
.filename Read and execute commands from filename and return. The search path specified by PATH is used to find the directory con-
taining filename.
C shell, csh
Built-in commands are executed within the C shell. If a built-in command occurs as any component of a pipeline except the last, it is exe-
cuted in a subshell. In addition to these built-in reserved command words, csh also uses:
: Null command. This command is interpreted, but performs no action.
Korn Shell, ksh, Special Commands
Input/Output redirection is permitted. Unless otherwise indicated, the output is written on file descriptor 1 and the exit status, when
there is no syntax error, is zero.
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, following 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 word splitting and file name generation are not
performed.
In addition to these built-in reserved command words, ksh also uses:
* : [ arg ... ] The command only expands parameters.
* .file [ arg ..Read the complete file then execute the commands. The commands are executed in the current shell environment. The search
path specified by PATH is used to find the directory containing file. If any arguments arg are given, they become the posi-
tional parameters. Otherwise, the positional parameters are unchanged. The exit status is the exit status of the last com-
mand executed. the loop termination test.
intro(1), alias(1), break(1), cd(1), chmod(1), csh(1), echo(1), exec(1), exit(1), find(1), getoptcvt(1), getopts(1), glob(1), hash(1), his-
tory(1), jobs(1), kill(1), ksh(1), let(1), limit(1), login(1), logout(1), newgrp(1), nice(1), nohup(1), print(1), pwd(1), read(1), read-
only(1), set(1), sh(1), shift(1), suspend(1), test(1B), time(1), times(1), trap(1), typeset(1), umask(1), wait(1), chdir(2), chmod(2),
creat(2), umask(2), getopt(3C), profile(4), environ(5)
29 Jun 2005 shell_builtins(1)