12-17-2013
When you use
./test4.sh, then the script is "executed" by the kernel. Now the script is just text and not a executable binary. So the kernel needs to execute an "interpreter" instead. If the file starts with
#!, then the kernel recognizes this and executes the program defined between
#! and the first newline character. The name of the script is passed as commandline argument to the interpreter.
When you type
sh test4.sh, then you directly call the program
sh and pass the scriptname on the commandline. The first line of the script is just a comment in this case and has no special meaning.
You can find more information here:
Shebang (Unix) - Wikipedia, the free encyclopedia
This User Gave Thanks to hergp For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
In my shell script when I am using mv command using shell variables it is giving me error of syntax. Following is the shell script:
file_edifice="*.txt"
fquote="'"
fdquote=\"
for file in $file_edifice
do
file_name=$fquote$file$fquote
tofile_name=`date... (5 Replies)
Discussion started by: gammit
5 Replies
2. UNIX for Advanced & Expert Users
Hi All,
i have an small issue...
echo " "
eval x=$@
export x=`echo $x`
echo $x
ssh user@ipadrss; cd /mbbv/home/;
cd /mbbv/home/orange/orange/
echo pwd
bash samplescript.sh $x
above is my script which will triger from server A and will connect to server B for some... (2 Replies)
Discussion started by: Shahul
2 Replies
3. Shell Programming and Scripting
Hi,
I have script which is properly running but when i schedule it in cron it throws an error like :
Your "cron" job on retrprdapp1
/usr/bin/sh /retr/cron/ftp.sh 2>&1
produced the following output:
/retr/cron/ftp.sh: syntax error at line 17: `(' unexpected
line17 is
# Get list of... (10 Replies)
Discussion started by: rajagasti
10 Replies
4. Shell Programming and Scripting
Hi,
We check the printer status at the command line by giving the following command and the system gives an output;
lpstat -prn001_hp4000n
When I give the same command in a UNIX script the system gives an error while running the script as "lpstat: not found".
Please let me know... (8 Replies)
Discussion started by: jmathew99
8 Replies
5. Shell Programming and Scripting
Below part of script, is working fine sometimes and gives error sometime.
I am doing float operations, checking if x > y.
##########CODE##########
THRESHOLD="1.25"
ratio=$( echo "scale=2; ${prev}/${current}" | bc )
if ; then
split_date=`echo ${line} | cut -d, -f2`
fi ... (9 Replies)
Discussion started by: manishma71
9 Replies
6. Shell Programming and Scripting
Hi,
My script is working fine in AIX but throwing an error in SOLARIS system.
Here is the error message that I am getting when calculating the elapsed time:
/home/x772525/FindETA.sh: start_mins = *60 + : syntax error
.
((start_mins = $(expr substr "$j" 1 2)*60 + $(expr substr "$j" 4... (6 Replies)
Discussion started by: ajayakunuri
6 Replies
7. AIX
Hi,
# lspath
Missing hdisk0 fscsi0
Missing hdisk1 fscsi0
Missing hdisk2 fscsi0
Missing hdisk3 fscsi0
Missing hdisk4 fscsi0
Missing hdisk5 fscsi0
Missing hdisk6 fscsi0
Missing hdisk7 fscsi0
Missing hdisk8 fscsi0
Missing hdisk9 fscsi0
Missing hdisk10 fscsi0
Missing hdisk11... (2 Replies)
Discussion started by: JATA01
2 Replies
8. Shell Programming and Scripting
Hi,
I simply want to kill a running process using a script that read pid from a file and tries to kill it .Getting error as shown below code..
cat $HOME/BackupScript.ksh.run | head -1 | while read pid
do
ps -p $pid > /dev/null 2>&1
if ; then
kill -9 $pid
else
echo "no running $pid... (5 Replies)
Discussion started by: dhirajdsharma
5 Replies
9. Shell Programming and Scripting
cat test3.sh
#!/bin/sh
set -x
while getopts ":n:" opt; do
case "$opt" in
n)
host=$OPTARG
shift 2
;;
-h )
host=$2
shift 2
;;
*)
break
;;
esac
done;
echo "host =... (7 Replies)
Discussion started by: Vishal_dba
7 Replies
10. HP-UX
Hi All,
We are getting a very unique error while running a shell script on HP-UX box.
Can somebody help in this regards?
The shell script is working fine on linux/solaris box.
Error:
++++++++++++++++++++++++
$/test.sh
./test.sh: 0^J30: Syntax error
$
++++++++++++++++++++++++
TIA.... (16 Replies)
Discussion started by: vai_sh
16 Replies
scotty(1) Tnm Tcl Extension scotty(1)
__________________________________________________________________________________________________________________________________________________
NAME
scotty - A Tcl shell including the Tnm extensions.
SYNOPSIS
scotty ?fileName arg arg ...?
_________________________________________________________________
DESCRIPTION
scotty is a Tcl interpreter with extensions to obtain status and configuration information about TCP/IP networks. After startup, scotty
evaluates the commands stored in .scottyrc and .tclshrc in the home directory of the user.
SCRIPT FILES
If scotty is invoked with arguments then the first argument is the name of a script file and any additional arguments are made available to
the script as variables (see below). Instead of reading commands from standard input scotty will read Tcl commands from the named file;
scotty will exit when it reaches the end of the file.
If you create a Tcl script in a file whose first line is
#!/usr/local/bin/scotty2.1.11
then you can invoke the script file directly from your shell if you mark the file as executable. This assumes that scotty has been
installed in the default location in /usr/local/bin; if it's installed somewhere else then you'll have to modify the above line to match.
Many UNIX systems do not allow the #! line to exceed about 30 characters in length, so be sure that the scotty executable can be accessed
with a short file name.
An even better approach is to start your script files with the following three lines:
#!/bin/sh
# the next line restarts using scotty
exec scotty2.1.11 "$0" "$@"
This approach has three advantages over the approach in the previous paragraph. First, the location of the scotty binary doesn't have to
be hard-wired into the script: it can be anywhere in your shell search path. Second, it gets around the 30-character file name limit in
the previous approach. Third, this approach will work even if scotty is itself a shell script (this is done on some systems in order to
handle multiple architectures or operating systems: the scotty script selects one of several binaries to run). The three lines cause both
sh and scotty to process the script, but the exec is only executed by sh. sh processes the script first; it treats the second line as a
comment and executes the third line. The exec statement cause the shell to stop processing and instead to start up scotty to reprocess the
entire script. When scotty starts up, it treats all three lines as comments, since the backslash at the end of the second line causes the
third line to be treated as part of the comment on the second line.
VARIABLES
Scotty sets the following Tcl variables:
argc Contains a count of the number of arg arguments (0 if none), not including the name of the script file.
argv Contains a Tcl list whose elements are the arg arguments, in order, or an empty string if there are no arg arguments.
argv0 Contains fileName if it was specified. Otherwise, contains the name by which scotty was invoked.
tcl_interactive Contains 1 if scotty is running interactively (no fileName was specified and standard input is a terminal-like device), 0
otherwise.
PROMPTS
When scotty is invoked interactively it normally prompts for each command with ``% ''. You can change the prompt by setting the variables
tcl_prompt1 and tcl_prompt2. If variable tcl_prompt1 exists then it must consist of a Tcl script to output a prompt; instead of out-
putting a prompt scotty will evaluate the script in tcl_prompt1. The variable tcl_prompt2 is used in a similar way when a newline is typed
but the current command isn't yet complete; if tcl_prompt2 isn't set then no prompt is output for incomplete commands.
SEE ALSO
Tnm(n), Tcl(n)
AUTHORS
Juergen Schoenwaelder <schoenw@cs.utwente.nl>
Tnm scotty(1)