perl limitations vs. bash? Post: 302421533

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

mkdir limitations

What characters can't be used with a mkdir? Any limits on length of name? Thank you, Randy M. Zeitman http://www.StoneRoseDesign.com

2. UNIX for Dummies Questions & Answers

Hi All, I want to sort a flat file which will contain millions of records based on a key/field. For this I want to use unix sort command and before that I want to make sure that unix sort command has any file size limitations. And also please let me know whether I have to change any...

3. AIX

SORT Command Limitations

Hi every body, On AIX 4.3.3 what is the maximum file size that can be used with sort command?

4. UNIX for Dummies Questions & Answers

csplit limitations

I am trying to use the csplit file on a file that contains records that have more than 2048 characters on a line. The resultant split file seems to ignore the rest of the line and I lose the data. Is there any way that csplit can handle record lengths greater than 2048? Thanks

5. UNIX for Dummies Questions & Answers

Password limitations.

I would like to set my minimum password length to on Linux and AIX. However, doing this normally would only make it so newly added users will be affected by this. I would like for when I make this change, it either truncates everyone elses password, or prompts them to change it to 8+ characters....

6. Shell Programming and Scripting

passing variable from bash to perl from bash script

Hi All, I need to pass a variable to perl script from bash script, where in perl i am using if condition. Here is the cmd what i am using in perl FROM_DATE="06/05/2008" TO_DATE="07/05/2008" "perl -ne ' print if ( $_ >="$FROM_DATE" && $_ <= "$TO_DATE" ) ' filename" filename has...

7. UNIX and Linux Applications

gnuplot limitations

I'm running a simulation (programmed in C) which makes calls to gnuplot periodically to plot data I have stored. First I open a pipe to gnuplot and set it to multiplot: FILE * pipe = popen("gnuplot", "w"); fprintf(pipe, "set multiplot\n"); fflush(pipe); (this pipe stays open until the...

8. Red Hat

Eth0 Limitations

Hi, I have noticed some performance issues on my RHEL5 server but the memory and CPU utilization on the box is fine. I have a 1G full duplexed eth0 card and I am suspicious that this may be causing the problem. My eth0 settings are as follows: Settings for eth0: Supported ports: ...

9. Solaris

Solaris limitations

Hi, I recently started working with Solaris, and what I noticed is that a lot of commands I used to regularly use don't work, like sed -i and grep -r. I have found work arounds for these problems though but it's a pain in the ass. I'm just wondering why they decided not to include these handy...

10. Linux

Linux partitions and limitations

In recently reading an article on linux basics before I embark and my personal installation project I came across this passage - IDE drives have three types of partition: primary, logical, and extended. The partition table is located in the master boot record (MBR) of a disk. The MBR is the...

LEARN ABOUT LINUX

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 1.8.5.3							    01/14/2014							  GIT-PACK-REFS(1)

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

mkdir limitations

Discussion started by: flignar

2. UNIX for Dummies Questions & Answers

Unix Sort - Limitations

Discussion started by: chprvkmr

3. AIX

SORT Command Limitations

Discussion started by: aldowsary

4. UNIX for Dummies Questions & Answers

csplit limitations

Discussion started by: ravagga