01-18-2012
Yes, I have never had a dot in $PATH for the reason you stated and I think "sh scriptname" always worked if scriptname was in the current directory (perhaps similar to any command that uses a file, where you also don't need to specify the path), as long as it is readable (even though I habitually execute with "sh ./scriptname").
Just "scriptname" is a different matter, that only works without a path if it is in $PATH and if it is both readable and executable (aliases aside).
Last edited by Scrutinizer; 01-18-2012 at 02:44 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
Can somebody tell me the differnce between a call of a ksh with the dot :
>. script.ksh
and the call without the dot:
>script.ksh
In my script I have writen a test for the number of parameters:
if
then echo 'Usage : '$0
exit 1
fi
as my script doesn't need any... (3 Replies)
Discussion started by: Cecile
3 Replies
2. Shell Programming and Scripting
Hi,
Please help me on the below code of line of what it actually does
${Script_dir}/scrip1.sh &
export script1_pid=$!
${Scipt_dir}/script2.sh &
export script2_pid=$!
${Scrip_dIR}/script3.sh &
export script3_pid=$!
wait ${script1_pid} //could u tell me wht this... (8 Replies)
Discussion started by: sussane
8 Replies
3. Shell Programming and Scripting
The situation is like this.
If I need to know the parameters of all the unix servers connected to a common network, is it possible to get all the parameter details of all the system with the help of a script written in one server??
Can a script be written like that ?
Let me give some... (3 Replies)
Discussion started by: yuvanash
3 Replies
4. Shell Programming and Scripting
I have an expect script that interrogates several hundred unix servers for both access and directories therein using "ssh user@host ls -l /path". The combination of host/path are unique but the host may be interrogated multiple times if there are multiple paths to test.
The expect script is run... (2 Replies)
Discussion started by: twk
2 Replies
5. Shell Programming and Scripting
Hello all,
I generally get 6 or more files at location /usr/example.Files listed below
er 1 2 3 9.txt
er 2 2 3 9.txt
er 3 2 3 9.txt
er 4 2 3 9.txt
abc.next
del pa.txt
cr ad.txt
ps tr as er.txt
Now the issue is i need to transfer 2 files (one file is fixed called abc.next) at a... (12 Replies)
Discussion started by: j_panky
12 Replies
6. UNIX for Advanced & Expert Users
Hello,
I am writing a shell script in which i do ssh to remote server and count the number of files there and then exit. After the exit the shell script terminates which i believe is expected behavior. Can some one suggest me a way where even after the exit the script execution resumes.
... (2 Replies)
Discussion started by: manaankit
2 Replies
7. Emergency UNIX and Linux Support
I am database guy and not very good at shell scripts. I am seeking help to sharp my script coding. I have 5 scripts
1. master script. I use this one to call other four scripts to do database work.
2. db_backup_1 and log_backup_1
3. db_backup_2 and log_backup_2
in master script, I want to... (4 Replies)
Discussion started by: duke0001
4 Replies
8. Solaris
Hi,
I am having a shell script on Solaris 10 which has a while loop as shown below.
#!/usr/bin/ksh
#
while
do
sleep 60
done
Name of the shell script is coldcentric.sh. I executed script /DATAWAREHOUSE/LOAD/Scripts/coldcentric.sh from a command task in Informatica worklow as... (3 Replies)
Discussion started by: chekusi
3 Replies
9. Shell Programming and Scripting
My script that I wrote is no longer running, but just freezing when I execute it.
Before it was running and showing me where errors were, now when I execute it, nothing happens and i cant type anything into the command screen.
The script was a looping script, what could be going on? (8 Replies)
Discussion started by: MJCreations
8 Replies
10. UNIX for Advanced & Expert Users
I need to call a script if the month end falls on Saturday or Sunday (5 Replies)
Discussion started by: bala1985
5 Replies
LEARN ABOUT DEBIAN
plack::middleware::lighttpdscriptnamefix
Plack::Middleware::LighttpdScriptNameFix(3pm) User Contributed Perl Documentation Plack::Middleware::LighttpdScriptNameFix(3pm)
NAME
Plack::Middleware::LighttpdScriptNameFix - fixes wrong SCRIPT_NAME and PATH_INFO that lighttpd sets
SYNOPSIS
# in your app.psgi
use Plack::Builder;
builder {
enable "LighttpdScriptNameFix";
$app;
};
# Or from the command line
plackup -s FCGI -e 'enable "LighttpdScriptNameFix"' /path/to/app.psgi
DESCRIPTION
This middleware fixes wrong "SCRIPT_NAME" and "PATH_INFO" set by lighttpd when you mount your app under the root path ("/"). If you use
lighttpd 1.4.23 or later you can instead enable "fix-root-scriptname" flag inside "fastcgi.server" instead of using this middleware.
CONFIGURATION
script_name
Even with "fix-root-scriptname", lighttpd still sets weird "SCRIPT_NAME" and "PATH_INFO" if you mount your application at "" or
something that ends with "/". Setting "script_name" option tells the middleware how to reconstruct the new correct "SCRIPT_NAME" and
"PATH_INFO".
If you mount the app under "/something/", you should set:
enable "LighttpdScriptNameFix", script_name => "/something";
and when a request for "/something/a/b?param=1" comes, "SCRIPT_NAME" becomes "/something" and "PATH_INFO" becomes "/a/b".
"script_name" option is set to empty by default, which means all the request path is set to "PATH_INFO" and it behaves like your
fastcgi application is mounted in the root path.
AUTHORS
Yury Zavarin
Tatsuhiko Miyagawa
SEE ALSO
Plack::Handler::FCGI <http://github.com/miyagawa/Plack/issues#issue/68> <https://redmine.lighttpd.net/issues/729>
perl v5.14.2 2011-02-27 Plack::Middleware::LighttpdScriptNameFix(3pm)