Now I understand what you mean ok...
There is nothing to reset as shell scripts usually don't remember anything without writing it to a file or exporting it to the environment. So there is nothing to reset.
The problem with your script is the line
Quote:
f [ $# != 2 ]
which you should try with
Code:
if (( $# != 2 ))
The double round brackets treat the values as numbers (arithmetic), not as strings, so it should work now.
Example:
Code:
root@isau02:/data/tmp/testfeld> cat script.ksh
#!/usr/bin/ksh
echo $#
if (( $# != 2 )); then
echo "Hey! This is not 2 parameters!"
else
echo "Everything is fine"
fi
exit 0
root@isau02:/data/tmp/testfeld> ./script.ksh b lala
2
Everything is fine
root@isau02:/data/tmp/testfeld> ./script.ksh b lala lal
3
Hey! This is not 2 parameters!
root@isau02:/data/tmp/testfeld> ./script.ksh yo
1
Hey! This is not 2 parameters!
EDIT: Oh didn't notice he was sourcing, forget my post
HPUX11.0/Korn Shell
I have an old script that takes in a series of arguments when its called. The script is really more of a common set of functions that gets called by other scripts as needed. I have been asked to make this into a menu driven script to rollout to app support for their use during... (2 Replies)
Hello,
I am using the Bourne shell.
I am trying to understand the concept of positional parameters.
I do understand that positional parameters:
1. Are initialized by shell
2. Have a max of 9 parameters ($1 to $9)
3. Have no limit on the number of arguments
4. Can be rearranged... (15 Replies)
I need to get file names from commandline arguments, it may be any no of arguements, Using for loop i got but how do i display it, bcoz $i will give the number i is assigned $$i is not working either $($i), i need the names of the files got in the arguement (2 Replies)
Hi all,
I have one small requirment...
I have prepared one script. we have to pass two possitional parameters to the script. What I want to do is if the parameters are not passed then i dont want the script to start the process...
For ex:
$ ./a.sh parm1 parm2
#Here, it can start... (7 Replies)
In a Bash script I used getopts command to let a user does something regards to the selected options. The question is: How do you find out what is the name of the file that user inserted in the command line like the following:
The good part is this file is always the last argument in the... (2 Replies)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
STEP 1: Create a Bash shell script (myscript) inside the a2 directory. The script should allow the user to pass... (3 Replies)
Hi,
Sorry for a dummy question I believe. I am just wanting to know how do I assign a default $1 argument if one is not provided.
At the moment, I am doing something like below:
arg1="${1:-foo}"And then I check $arg1 in case/esac. I am just wondering if there is a way for me to simply do... (3 Replies)
I'm new with 'sed' and for sure something still I don't understand yet with it. If you see my output on ">Output..." portion, the new directory still on "source_dir" instead of "dest_dir". You may disregard for the "tar" part, this is just a test script, just for me to understand 'sed' using the... (3 Replies)
I am trying to code an if statement that accepts two parameters and see if those parameters are in another file called teledir.txt. If it already exists in the file, it is to say "Entry Exists". If not, I add it to the file and say "Entry Added". This is the code I have so far:
if ; then
... (1 Reply)
Discussion started by: Eric7giants
1 Replies
LEARN ABOUT SUNOS
for
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)
07-16-2008
