Issue on new server

Shell Programming and Scripting
1

I use to run my scripts by .test.ksh now I have to do ./test.sh.

I think something is not correctly set up on the server. Can someone tell me the difference between . and ./

I though ./ meant force the script to run even it cannot find the path of way the script actually is?

---------- Post updated at 03:28 AM ---------- Previous update was at 03:26 AM ----------

typeo error

I use to run my scripts by .test.ksh now I have to do ./test.ksh.

I think something is not correctly set up on the server. Can someone tell me the difference between . and ./

I though ./ meant force the script to run even it cannot find the path of way the script actually is?

2

the PATH settings could be wrong. check the PATH on old and new server...

3

The PATH variable is the problem.

When PATH has a single dot in it -- that means to search the current directory for the executable. . == current working directory

No dot means that you have to use ./ unless the directory is defined in PATH

example

cd /home/me
PATH=.:/usr/bin:/usr/sbin
# this will execute a script in /home/me
myscript.shl
PATH=/usr/bin:/usr/sbin
# this will not work now
myscript.shl
# this will execute the script now
./myscript.shl

WARNING - having a . in your PATH can be a security risk. root and other privileged accounts should never, ever have a dot in the PATH variable.