02-19-2007
can't understand this at all.
Ok, i've been trying to write some shell scripts. nothing challenging, but just automating
All of the tutorials i read say to start the file with
#!/bin/bash
or whatever your path to bash is.
So i do it, and all of my scripts error out saying ./nameofscript:command not found
when i remove the line completely the script seems to run ok. Why??
I understand the easy answer is to say "so just leave the line out" but I really would like to understand why it's happening.
thanks,
chris
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
how i can download this game n start it :S (5 Replies)
Discussion started by: BoyArcher
5 Replies
2. Shell Programming and Scripting
The following regular expression is found in a book I have been reading. It apparently can be used on an /etc/passwd file to find any accounts which have no password. I am having a heck of a time seeing how it works, and I was wondering if someone could run me through it. I will take a stab at... (1 Reply)
Discussion started by: kermit
1 Replies
3. Solaris
I'm new to unix so sorry for the confusing question.
I installed OPENSSL following these instructions.
Installing OpenSSH Packages - SPARC and Intel/Solaris 8
I need to run this command, "openssl req -newkey rsa:1024 -keyout server.pf.key -out req.pem" from a keyreq folder I created.
... (13 Replies)
Discussion started by: Kjons76
13 Replies
4. Programming
Hi all,
I'm a user and a programmer of UNIX based systems (mainly FreeBSD and Linux).
I have never programmed or tried to fully understand the kernel layer. I haven't a special propouse for learning it, but I'd like to. Can anyone suggest me books, documentation or examples that may help me... (2 Replies)
Discussion started by: mghis
2 Replies
5. Shell Programming and Scripting
Hi All,
Good day, i'm just wondering what is the meaning of this code?
COUNT_EXTRACTED_FILE=`${ECHO_CMD} "${SE_IN_PATH}${SE_IN_FILE}" | ${AWK_CMD} -F"__" '{print $2}'`
Thanks,
-niks(newbie) (2 Replies)
Discussion started by: nikki1200
2 Replies
6. Shell Programming and Scripting
Hi All,
can you please help me to figured out what's the meaning of this.
${SERVER_DATABASE} -b << EOF 2>>/dev/null
THanks, (3 Replies)
Discussion started by: nikki1200
3 Replies
7. Shell Programming and Scripting
Hi ,
i am in my initial learning phase of unix. i was going thru the function part.
below is the example which was there but i am not able to understand logic and the use of IFS(internal field separator)
lspath() {
OLDIFS="$IFS"
IFS=:
for DIR in $PATH ; do echo $DIR ; done
IFS="$OLDIFS"... (8 Replies)
Discussion started by: scriptor
8 Replies
8. Shell Programming and Scripting
cat teledir.txt
jai sharma 25853670
chanchal singhvi 9831545629
anil aggarwal 9830263298
shyam saksena 23217847
lalit chowdury 26688726
If i use the below command , it is giving me the output with "," in between two name. how ? and also i would like to know the reason for the space used in... (1 Reply)
Discussion started by: Antony Ankrose
1 Replies
LIBBASH(7) libbash Manual LIBBASH(7)
NAME
libbash -- A bash shared libraries package.
DESCRIPTION
libbash is a package that enables bash dynamic-like shared libraries. Actually its a tool for managing bash scripts whose functions you may
want to load and use in scripts of your own.
It contains a 'dynamic loader' for the shared libraries ( ldbash(1)), a configuration tool (ldbashconfig(8)), and some libraries.
Using ldbash(1) you are able to load loadable bash libraries, such as getopts(1) and hashstash(1). A bash shared library that can be loaded
using
ldbash(1) must answer 4 requirments:
1. It must be installed in $LIBBASH_PREFIX/lib/bash (default is /usr/lib/bash).
2. It must contain a line that begins with '#EXPORT='. That line will contain (after the '=') a list of functions that the library
exports. I.e. all the function that will be usable after loading that library will be listed in that line.
3. It must contain a line that begins with '#REQUIRE='. That line will contain (after the '=') a list of bash libraries that are
required for our library. I.e. every bash library that is in use in our bash library must be listed there.
4. The library must be listed (For more information, see ldbashconfig(8)).
Basic guidelines for writing library of your own:
1. Be aware, that your library will be actually sourced. So, basically, it should contain (i.e define) only functions.
2. Try to declare all variables intended for internal use as local.
3. Global variables and functions that are intended for internal use (i.e are not defined in '#EXPORT=') should begin with:
__<library_name>_
For example, internal function myfoosort of hashstash library should be named as
__hashstash_myfoosort
This helps to avoid conflicts in global name space when using libraries that come from different vendors.
4. See html manual for full version of this guide.
AUTHORS
Hai Zaar <haizaar@haizaar.com>
Gil Ran <ril@ran4.net>
SEE ALSO
ldbash(1), ldbashconfig(8), getopts(1), hashstash(1) colors(1) messages(1) urlcoding(1) locks(1)
Linux Epoch Linux