1748175 Members
4165 Online
108758 Solutions
New Discussion юеВ

Re: script problem

 
Howard Marshall
Regular Advisor

Re: script problem

Oh yea. To answer your original question, the dot slash ./ is a relative path name where the dot . represents the current working directory as returned by the pwd command. The slash separates the directory from the filename of the script. So, if you change to the /usr/contrib/bin directory and execute /usr/contrib/bin/gzcat it would be the equivalent of ./gzcat sense . will translate to /usr/contrib/bin
Arturo Galbiati
Esteemed Contributor

Re: script problem

Hi,
test is a ksh command so you have to use ./ to inform the shell that you want to execute your script and not the bulldin command.
rename your script as test.ksh and you can simple test.ksh to invoke it (if you have . in teh PATH).
HTH,
Art
RAC_1
Honored Contributor

Re: script problem

first test is not a good name for the script. test is built in command for most of the shells.
Do following to know what exactly you will be executing.

type test

If you want to execute yout script names test, give full path when starting it.

/some_dir/some_dir/test
There is no substitute to HARDWORK