Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

RackTables 0.16.4 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News RackTables 0.16.4 (Default branch)
# 1  
Old 11-04-2008
RackTables 0.16.4 (Default branch)
Image RackTables is a tool to manage tens of racks, hundreds of servers, and thousands of MAC and IP addresses. It will work with a single rack as well. It features a real-life rackspace model, typed rack objects with flexible attribute sets, a tagging system, IP address management ready for NAT, virtual routers and load balancers, accurate network connection handling, a universal search function, a multi-user access model, and an extensible dictionary. License: GNU General Public License v2 Changes:
This routine release fixes many small annoying bugs related to data input and output. A notable update to SNMP code was made. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

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)