I guess there is a bug in your bash, or there is a bug in the terminal definition it uses, or it was build with a different one.
What's your OS?
What's the path to bash?
Hello,
AIM: Need to test for the presence of some files (*.F) in a certain directory.
having a problem with this line is ksh:
if test `ls $SOMEDIR/dir/*.F \
2>/dev/null|wc -w` -eq 0
Basically testing for the presence of *.F files in the specified directory. If the return... (4 Replies)
In a BASH library I'm creating, I have two functions that look like:
function check_process {
PIDFILE=$1
if ; then
PID=`cat $PIDFILE`
if && ; then
return 1
fi;
fi;
return 0
}
function fork_process {
CMD=$1
PIDFILE=$2
... (2 Replies)
Hi Gurus,
I have a big file having around 5000 lines. What I need to do is as below.
$cat myfile
aaaa
bbbb
ccc
ddd
...
I want the output to be as below:
'aaaa,'bbbb','cccc'....
For this I have written something like this
code:
vi sac.txt |nawk '{printf NR","}'>ss
code: (2 Replies)
I'm using a barcode scanner to grab ISBNs. Unfortunately, short of hitting "enter" each time (not easy while on a ladder), there's no good way to split it up. So I scanned it into a series of long lines in notepad.
Now, I need to split each line into 12-number lines.
instead of:... (4 Replies)
Greetings!
Some of my files list hardware errors (we test electronic components), some have none. If the file name has no errors, I still want to display a message like "No error", else I display the error from the file itself.
I came up with this (with help)
for myfile in `find . -name... (2 Replies)
Does anyone know of any script or packages that allow the calculation of the geographical distance between two points of lat/long from within a bash shell?
I have been searching the web for the past few days and none of the options seem compatible with bash variables... (eg. geodist)
Many... (3 Replies)
Hi,
I'm trying make a variable length file to a fixed length of 4000.
I'm to pad spaces on the right of a record if length is less than 4000 to make the record length 4000.
I'm trying to use the below commands
awk '{printf "%-4000s\n", $0}' inputfile.dat > outputfile.dat
sed -e :a... (12 Replies)
Greetings fellow scripters.
I find myself editing multiple files, sometimes with the same bits of information. My bash script, a changelog, and a plist file (OS X). Once I realized this, I thought why not script part of this process (and so it begins). In any case, I've solved several of the... (1 Reply)
I had been looking at page 75 of this online book:
http://richard.esplins.org/static/downloads/linux_book.pdf
I've used the system function in C to call bash commands before, but wanted to learn this way too. The solution in the book worked perfectly. However, I tried changing the simple "ls -l... (3 Replies)
Discussion started by: Azrael
3 Replies
LEARN ABOUT HPUX
libbash
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