02-16-2011
thank you all, those tips have done the trick!
8 More Discussions You Might Find Interesting
1. AIX
hi ,
i have made a mistake :( on the production enviourment by change tha host name .
after that i returned back the old name.
but i think this will not afeect the system until reboot the machine.
laso i tried to telnet the syetem by the host name not by the IP address and it works fine.
... (2 Replies)
Discussion started by: habuzahra
2 Replies
2. Linux
what is the difference between
uname -m and uname -i
what it actually means (2 Replies)
Discussion started by: Dileepsp
2 Replies
3. Solaris
hi all,
Operating System Name : Unix Sun Solaris
Operating system release level : 5.10
Operating system version : Generic_137111-06
i know the release level that is kernel version
Generic_137111-06 what is number... (6 Replies)
Discussion started by: coxmanchester
6 Replies
4. UNIX for Dummies Questions & Answers
Hi,
Can anyone let me know the -n option in uname command in unix?
Gone through the man pages of uname, but unable to interpret.
Thanks in advance. (1 Reply)
Discussion started by: venkatesht
1 Replies
5. UNIX for Advanced & Expert Users
Using the command :
echo $eup_terminal_code | tr -s 'mil vrn qcm' 'mci pql qcm'
it works,but this translation changes depending on the system.
I'd like to define the following variables ,one for each system :
mil22h_from='mil vrn frl'
mil22h_to='mci vci fci'
... (4 Replies)
Discussion started by: Pierluigi.sala
4 Replies
6. UNIX for Dummies Questions & Answers
Can anyone please let me know the meaning of output of uname -a ?
I am totally new to unix or linux and just thinking to start learning.
When I run uname -a the output I get is -
"Linux blx28ap01 2.6.18-238.12.1.el5 #1 SMP Sat May 7 20:18:50 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux"
I want to... (7 Replies)
Discussion started by: csrohit
7 Replies
7. Solaris
bssmsrv223:/ 53 ] uname -a
SunOS bssmsrv223 5.10 Generic_118833-36 sun4u sparc SUNW,Sun-Fire-V245
bssmsrv223:/ 54 ]
what does 118833-36 denotes in Generic_118833-36 (2 Replies)
Discussion started by: hiten.r.chauhan
2 Replies
8. Linux
Hi,
What is the exact output tells me when i issued UNAME and WHO ?
Regards,
Nantha.Y (2 Replies)
Discussion started by: Nandy
2 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)