Community.UNIX.com login tips

7 More Discussions You Might Find Interesting

1. What is on Your Mind?

How Much Vacation Do You Take? | UNIX.com Community | Annual Vacation (YouTube)

Here is another simple YT video co-produced with our video partner. How Much Vacation Do You Take? | UNIX.com Community | Annual Vacation https://youtu.be/MSy553qS654 Background sound track is called "Caribbean Paradise" Sounds like something wisecracker would have played in one...

2. Web Development

Login in Unix

Can anyone plz share the HTML code for login in UNIX. I am not able to verify the password.

3. UNIX for Dummies Questions & Answers

Learning Tips - UNIX Shell Script

Can any one please provide a fast learning tips to learn UNIX shell scripting? Thanks, Gov

4. Shell Programming and Scripting

Need UNIX Login ...

Hi, I dont have UNIX os on my pc. I want to learn UNIX system programming. How to get this OS or Can i get any remote login account ? Thanks. Bye...

5. UNIX for Advanced & Expert Users

UNIX login ID

Hello World: I need to have a user ID called devapp in the passwd and shadow file for a certain application to start. The problem is that I do not want users to be able to use the devapp login ID to log directly into the system. The users sometimes need to start and stop the...

6. UNIX for Dummies Questions & Answers

UNIX community...help your Mac brother!

Hello, I have been a Macintosh user for many, many years. As you may know the latest MacOS ( OS X ) is UNIX based. (Please see http://www.apple.com/macosx/technologies/inside.html for more information.) Basically, I really have no idea where to start with UNIX...if anyone could take a quick...

7. News, Links, Events and Announcements

Good tips to Unix System Administrator

A list with sites that have a good tips to Unix System Administrator : www.samag.com www-1.ibm.com/servers/aix/products/aixos/whitepapers/aixmapping.html www.science.uva.nl/pub/solaris/solaris2/index.html www.spec.org Witt

LEARN ABOUT MOJAVE

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)

What is on Your Mind?