09-17-2008
THX for the tips - gave me a solution.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
:confused: Hi, does anyone here know how to compile and run C++ in UNIX environment? I am so desperate! Any help is greatly appreciated. Thanks! (3 Replies)
Discussion started by: Kahuashi
3 Replies
2. UNIX for Dummies Questions & Answers
Hi I've written a a script on box A that ssh's into box B and runs another script. If I run the script on box B it works. However when I run my ssh script (public key setup so no passwd required) it fails with "The WSB_HOME environment variable is not defined". Checked wapuser1 .profile on box B... (1 Reply)
Discussion started by: alien12
1 Replies
3. UNIX for Dummies Questions & Answers
Hi guys,
thanks in advance for this easy answer.... :s
Ok I am trying to output the enviroment varable for host in Solaris. I have tried $HOST, $HOST_NAME, $HOSTNAME carn't find it anywhere, does someone want to put me out of my misary and tell me what it is??? :confused: :eek:
Thanks... (2 Replies)
Discussion started by: B14speedfreak
2 Replies
4. Solaris
Hello...
I was wondering can anyone explain me how to set up enviroment variable to be permanent...
I tryed with setenv but my solaris does not have this command...
then I did:
export ORACLE_SID=base1
export ORACLE_BASE=/home
export ORACLE_HOME=$ORACLE_BASE/oracle/8.1.6
and by... (5 Replies)
Discussion started by: amon
5 Replies
5. Programming
Hello!
Can somebody tell my where to find Solaris C compiler for Unix environment?
Is it available anywhere on the net for free download ?
Thank you for your help!
:( (3 Replies)
Discussion started by: krasy
3 Replies
6. Shell Programming and Scripting
Im looking for any sample scripts that would output a current environment setup to a file and possibly then take 2 files and list any differences
This will allow us to quickly see any differences between environments in case of issue?
At a high level this would take Unix Kernel Params,... (2 Replies)
Discussion started by: JoeShmoe
2 Replies
7. Solaris
I need to save my enviroment variables,specially the $PATH.When I put it on .cshrc at next reboot I lost the configuration.How can avoid this?Thanks (2 Replies)
Discussion started by: bgf0
2 Replies
8. UNIX for Dummies Questions & Answers
Hello everyone,
I am currently trying to program in java in unix platform for the first time, so far it is OK as long as I use class libraries which come with java distribution. Unfortunately when I try to use external libraries I have to use -classpath option which I rather not doing all the... (1 Reply)
Discussion started by: run123
1 Replies
9. Shell Programming and Scripting
Hi Folks,
I have the below command that will kill all the process of an environment,
lets say if I have reached to the location cont directory under which I want to kill multiple process so the command will be ....
kill -9 `ps -ef | grep cont | grep -v grep | awk '{print $2}'`
Now please... (4 Replies)
Discussion started by: punpun66
4 Replies
10. Shell Programming and Scripting
Hi Gurus,
I am stuck on below issue.
in my .profile. I have two variable:
x=abc$123
t=xyz$
when running env command, I got below:
x=abc
t=xyz$
my OS is SunOS 5.10 sun4v sparc SUNW,SPARC-Enterprise-T5220
I am wondering why t=xyz$ shows exactly value?
I try below: (9 Replies)
Discussion started by: ken6503
9 Replies
LEARN ABOUT SUSE
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 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 stashing the refs in a single file, $GIT_DIR/packed-refs. When a ref
is missing from the traditional $GIT_DIR/refs hierarchy, it is looked up in this file and used if found.
Subsequent updates to branches always create new files under $GIT_DIR/refs hierarchy.
A recommended practice to deal with a repository with too many refs is to pack its refs with --all --prune once, and occasionally run git
pack-refs --prune. 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.
AUTHOR
Written by Linus Torvalds <torvalds@osdl.org[1]>
GIT
Part of the git(1) suite
NOTES
1. torvalds@osdl.org
mailto:torvalds@osdl.org
Git 1.7.1 07/05/2010 GIT-PACK-REFS(1)