01-13-2009
Ok .. If i understand it correctly ,
It is recommended always to use the variable with quotes especially during comparison to avoid such errors . Am I right ?
Thanx otheus again.
Learned some more tips
Raj.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have this following script below. Its searching a log file for 2 string and if found then write the strings to success.txt and If not found write strings to failed.txt . if one found and not other...then write found to success.txt and not found to failed.txt.
I want to optimize this... (3 Replies)
Discussion started by: amitrajvarma
3 Replies
2. UNIX for Dummies Questions & Answers
I've a script to do some snapshots but the time it does so is very different...
once i got a snapshot under 1 sec, on the other hand it took 3 sec, but nothing else changed, i didnt even move the cursor or something.
I put the script on a ramdisk and its faster, but still swing from under 1... (1 Reply)
Discussion started by: mcW
1 Replies
3. Shell Programming and Scripting
Hi All,
There is a script (test.sh) which is taking more CPU usage. I am attaching the script in this thread.
Could anybody please help me out to optimize the script in a better way.
Thanks,
Gobinath (6 Replies)
Discussion started by: ntgobinath
6 Replies
4. Emergency UNIX and Linux Support
Dear Forum experts
I have the below script which I made to run under bash shell, it runs perfectly for low records number, let us say like 100000. when I put all records (3,000,000), it's takes hours
can you please suggest anything to optimize or to run in different way :-|
{OFS="|";... (6 Replies)
Discussion started by: yahyaaa
6 Replies
5. Shell Programming and Scripting
Here is my code. What it does is it reads an input file (input.txt which contains roughly 2,000 search phrases) and searches a directory for files that contains the search phrase. The directory contains roughly 1900 files and 84 subdirectories. The output is a file (output.txt) that shows only the... (23 Replies)
Discussion started by: jl487
23 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I need a shell script to determine if a no. is either even, greater than 4, less than 8
SHELL : ksh
OS : RHEL 6
this is the if block of the script
mod=`expr $num % 2`
if || ||
then
echo "No. is either even or greater than 4 or less than 8"
fi
this code works... (2 Replies)
Discussion started by: sam05121988
2 Replies
7. Shell Programming and Scripting
Hello,
I'm wondering if there is a quicker way of doing this.
Here is my mv script.
d=/conversion/program/out
cd $d
ls $d > /home/tempuser/$$tmp
while read line ; do
a=`echo $line|cut -c1-5|sed "s/_//g"`
b=`echo $line|cut -c16-21`
if ;then mkdir... (13 Replies)
Discussion started by: whegra
13 Replies
8. Shell Programming and Scripting
data.file:
contact {
contact_name=royce-rolls
modified_attributes=0
modified_host_attributes=0
modified_service_attributes=0
host_notification_period=24x7
service_notification_period=24x7
last_host_notification=0
last_service_notification=0
host_notifications_enabled=1... (8 Replies)
Discussion started by: SkySmart
8 Replies
9. Shell Programming and Scripting
Hi All,
I have written a new script to check for DB space and size of dump log file before it can be imported into a Oracle DB.
I'm relatively new to shell scripting.
Please help me optimize this script further. (0 Replies)
Discussion started by: narayanv
0 Replies
10. Shell Programming and Scripting
Hi Friends,
I'm trying to create a script that allows me to recursively resize, crop (holding the center of the image) and optimize images jpg, jpeg, png for a specific folder and subfolder with the ability to exclude certain folder and its subdirectory.
Again, I should to do with this script:... (3 Replies)
Discussion started by: danjde
3 Replies
LEARN ABOUT OSX
git-pack-refs
GIT-PACK-REFS(1) Git Manual GIT-PACK-REFS(1)
NAME
git-pack-refs - Pack heads and tags for efficient repository access
SYNOPSIS
git pack-refs [--all] [--no-prune]
DESCRIPTION
Traditionally, tips of branches and tags (collectively known as refs) were stored one file per ref in a (sub)directory under $GIT_DIR/refs
directory. While many branch tips tend to be updated often, most tags and some branch tips are never updated. When a repository has
hundreds or thousands of tags, this one-file-per-ref format both wastes storage and hurts performance.
This command is used to solve the storage and performance problem by storing the refs in a single file, $GIT_DIR/packed-refs. When a ref is
missing from the traditional $GIT_DIR/refs directory hierarchy, it is looked up in this file and used if found.
Subsequent updates to branches always create new files under $GIT_DIR/refs directory hierarchy.
A recommended practice to deal with a repository with too many refs is to pack its refs with --all once, and occasionally run git
pack-refs. Tags are by definition stationary and are not expected to change. Branch heads will be packed with the initial pack-refs --all,
but only the currently active branch heads will become unpacked, and the next pack-refs (without --all) will leave them unpacked.
OPTIONS
--all
The command by default packs all tags and refs that are already packed, and leaves other refs alone. This is because branches are
expected to be actively developed and packing their tips does not help performance. This option causes branch tips to be packed as
well. Useful for a repository with many branches of historical interests.
--no-prune
The command usually removes loose refs under $GIT_DIR/refs hierarchy after packing them. This option tells it not to.
BUGS
Older documentation written before the packed-refs mechanism was introduced may still say things like ".git/refs/heads/<branch> file
exists" when it means "branch <branch> exists".
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-PACK-REFS(1)