How to remove old files without recursion? Post: 302189691

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

recursion

I'm using the UNIX csh and i wish to use recursion to nav my way up (or down as it is) a given folder. My little test script is called "r" and takes a folder as argv (or $1) #!/bin/tcsh -f set allFiles = `ls -A $argv` cd $argv while ($#allFiles) if (-d...

2. Shell Programming and Scripting

recursion too deep

I am running a korn shell script which has a recursive function. The script ran for 117 iterations and ended up with the following error "recursion too deep". what should be done to avert this? Thanks in advance Swamy p.s. I am on UNIX MPRAS V4

3. Shell Programming and Scripting

A Question On Recursion In Ksh

Hi Folks, I would just like to know how recursion works in ksh or inside a shell in general. I created the following script, but it works(runs recursively) only for 64 times: ---------------- #! /usr/bin/ksh displaymessage() { echo "displaying count: $cnt " echo "wait for 1 second..."...

4. Shell Programming and Scripting

Help Help Help in recursion

Hello every body. I am trying to find the factorial using the following code. But it is giving the syntax error. I tried very much but in vain. Thanks in advance for helping me factorial() { if then y=`expr $1 - 1` x=$(( $1 \* factorial $y ))...

5. Shell Programming and Scripting

diffrence in non recusion and recursion

Hi, If i have given to write a prog for factorial in C using recursion and without recursion which one is better in what condition and why ? thanks

6. Programming

Recursion

I want to halt a tail recursive function after certain validation. I want to come out of entire recursion without unwinding phase. How can i achieve that . The coding is done in C language.

7. Shell Programming and Scripting

recursion script problem

Hi Guys,, I tried to create a recursive function in unix. The following is the code. #/bin/sh function(){ n=$1; if ; then out=1; echo "inside if for 0"; else out = `$n * function "$n-1"`; echo "inside if for $n-1; fi

8. Programming

C Recursion (explain)

Hi, Question: how come the output is like that? Can explain to me abit. I am learning C. Thanks! #include <stdio.h> #include <string.h> void printit(char line_of_char, int index); int main() { char line_of_char; int index = -1; strcpy(line_of_char, "This is a string."); ...

9. Shell Programming and Scripting

script recursion

Can someone please explain me why the following script calls it self recursively: #!/bin/bash echo Called $0 while this not: #!/bin/bash echo Called $($0) Thanks

10. UNIX for Advanced & Expert Users

Recursion list for rm -R in find

In the following command: find / -ctime +3 -exec rm -R {}\; how is the recursion list built for the actual rm ? F'rinstance; I had a case where a user typed this as root using '/' instead of '.' so everything in the root level was going to be traversed. They hit <ctrl>C before too much was...

LEARN ABOUT SUSE

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 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 stashing the refs in a single file, $GIT_DIR/packed-refs. When a ref
       is missing from the traditional $GIT_DIR/refs hierarchy, it is looked up in this file and used if found.

       Subsequent updates to branches always create new files under $GIT_DIR/refs hierarchy.

       A recommended practice to deal with a repository with too many refs is to pack its refs with --all --prune once, and occasionally run git
       pack-refs --prune. 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.

AUTHOR

       Written by Linus Torvalds <torvalds@osdl.org[1]>

GIT

       Part of the git(1) suite

NOTES

	1. torvalds@osdl.org
	   mailto:torvalds@osdl.org

Git 1.7.1							    07/05/2010							  GIT-PACK-REFS(1)

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

recursion

Discussion started by: gsjf

2. Shell Programming and Scripting

recursion too deep

Discussion started by: swamy455

3. Shell Programming and Scripting

A Question On Recursion In Ksh

Discussion started by: marlonus999

4. Shell Programming and Scripting

Help Help Help in recursion

Discussion started by: murtaza