12-04-2008
the below is the statement in my script.
1. read -r variable < /path/file.txt
finalvar=${variable##*_}
2. MYNAME=${0##*/};
please let me know what it is actually doing.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Found this piece of code written in ksh. I have no ideas what do the stuff like ${SRF##*\.} do.
SUFFIX=${SRF##*\.}
if ; then
SUFFIX=""
fi
I have encountered similar expressions in other programs also. Any pointers on where to learn more about these... (1 Reply)
Discussion started by: jyotipg
1 Replies
2. Post Here to Contact Site Administrators and Moderators
woofie,
Your posts are being deleted because your use of profanity.
I am close to changing your status to read only.
In fact, if you argue with the mods again, I will ban you from these boards.
Neo (1 Reply)
Discussion started by: Neo
1 Replies
3. What is on Your Mind?
Looking at the member list, there are alot of interesting names, some unique, some bizarre, and some that are just plain. How did you come by your name? Why did you choose your label?
Me? Well, I wish I could change mine. I chose Google because thats how I stumbled upon this site. I wasn't sure... (66 Replies)
Discussion started by: google
66 Replies
4. Shell Programming and Scripting
Hi,
whats the difference between $* and $@ in command line arguments to a shell scripts (3 Replies)
Discussion started by: pbsrinivas
3 Replies
5. Shell Programming and Scripting
#! /bin/bash
head -5 $1
echo "remove $1 ?"
read answer
if
then
echo invalid answer
elif
rm $1
echo "$1 is deleted"
elif
then
echo file is not deleted
else
echo "invalid answer"
fi
What i really want this to do is to ask to delete the file or not..it says something wrong... (1 Reply)
Discussion started by: nadman123
1 Replies
6. Shell Programming and Scripting
#! /bin/bash
USAGE=" | ]
if
then
echo "$USAGE"
exit 1
fi
while getopts lb: OPTION
do
case $(OPTION)in
a) echo Hi there!
exit 2;;
b) echo hello
o) OARG=$OPTARG;;
\?)echo "$USAGE" ;;
exit 2;;
esac
done
shift `expr... (1 Reply)
Discussion started by: nadman123
1 Replies
7. Shell Programming and Scripting
hi all,
i found NAME=${0##*/} in a script.
i given this coomand in my unix box(presently in ksh).
echo ${0##*/} it returned ksh.
the purpose of the above is to return the shell name or more than that.
do you have any more information like this, please share with me.
one more query... (7 Replies)
Discussion started by: Arunprasad
7 Replies
8. UNIX for Dummies Questions & Answers
can anyone tell me why this code doesn't work how its supposed to, its the hangman game but it doesn't play how its supposed to
#!/bin/bash
NoAttempts="0"
livesgiven="5"
LivesRemain=$livesgiven
LettersAttempted=""
wordfile=words
numwords=0
function menu()
{
clear
cat << menu... (1 Reply)
Discussion started by: ferrycorsten73
1 Replies
9. Homework & Coursework Questions
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:
ls -ld htdocs
drwxr-x--- 3 root root 8192 2006-11-19 10:41 htdocs
How would a host administrator... (1 Reply)
Discussion started by: Larry_1
1 Replies
MAKESH(1) General Commands Manual MAKESH(1)
NAME
makeSH - a .SH script maker
SYNOPSIS
makeSH files
DESCRIPTION
MakeSH examines one or more scripts and produces a .SH file that, when run under sh, will produce the original script. The .SH script so
produced has two sections containing code destined for the output. The first section has variable substitutions performed on it (taking
values from config.sh), while the second section does not. MakeSH does not know which variables you want to have substituted, so it puts
the whole script into the second section. It's up to you to insert any variable substitutions in the first section for any values you want
from config.sh.
You should run makeSH from within your top-level directory and use the relative path to the file as an argument, so that the "Extracting
..." line printed while running the produced .SH file later on will give that same path.
AUTHOR
Larry Wall <lwall@netlabs.com>
SEE ALSO
pat(1), metaconfig(1), makedist(1).
BUGS
It could assume that variables from metaconfig's Glossary need to be initialized in the first section, but I'm too lazy to make it do that.
LOCAL MAKESH(1)