8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hello all,
I have recently acquired the above server and i am having issues with the RAID controllers being put into a lockdown state.
This occurs when new drives are added to the array, the controller automagically reboots and then gives status codes OE and LT. After this i am unable to... (0 Replies)
Discussion started by: WombleLord
0 Replies
2. Red Hat
Issue Description:
================
There are of 4 servers (SunFire X440) :
siman7tdw: SunFire X440 (affected server)
siman8tdw:SunFire X440 (affected server)
siman9tdw:SunFire X440
siman10tdw:SunFire X440
Storage Server: Sun Storage Tek 6140 (Name: simantdw_disk_bak) and Sun Storage... (1 Reply)
Discussion started by: Pawan Kumar
1 Replies
3. AIX
I'm trying to install libiconv to AIX 7.1 from an rpm off of the perzl site. The rpm appears to install but I get this error message.
add shr4.o shared members from /usr/lib/libiconv.a to /opt/freeware/lib/libiconv.a
add shr.o shared members from /usr/lib/libiconv.a to ... (5 Replies)
Discussion started by: kneemoe
5 Replies
4. Linux
Hello,
./configure script fails to configure libsf. Please check the following last few lines of configure script error.
checking for db1/db.h... no
checking for db.h... yes
checking for dbopen in -ldb1... no
configure: error: No libdb? No libsf.
But find command shows the following; ... (4 Replies)
Discussion started by: vectrum
4 Replies
5. UNIX for Dummies Questions & Answers
hi...
I want some tips for standardizing shell script code... (1 Reply)
Discussion started by: xerox
1 Replies
6. Shell Programming and Scripting
Hi:
I have a library that it only offers Makefile for building static library. It built libxxx.a file. How do I in any way build a shared library? (either changin the Makefile or direct script or command to build shared library)
Thanks. (1 Reply)
Discussion started by: cpthk
1 Replies
7. Solaris
hi all...
I need to know, how I can create a log when the user loggin and logout...day and hour....any person help me.....
thank you (7 Replies)
Discussion started by: chanfle
7 Replies
8. UNIX for Dummies Questions & Answers
I'm running a small FreeBSD 5.1 system @ home. Whenever you log in with a normal account (not root) the system displays a random tip (commands, etc.) after the MOTD. I'd like to turn this feature off so that my custom MOTD fits on one screen. Is this posible at all? (3 Replies)
Discussion started by: McFlashbang
3 Replies
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 1.8.5.3 01/14/2014 GIT-PACK-REFS(1)