I have a DOS script on Windows NT that uses FTP to connect to a Unix server and to copy files to the WinNT.
So far, so good.
Now I want to delete those files on Unix afterwards but I'm unable to delete all files in the directory. How can I delete all the files on Unix from where i did ftp all... (3 Replies)
Hi,
I've to delete certain files older than X days from a Maintenance server.
I'm doing this using
find . -name lds\* -mtime $X \
-exec ls -l {} \;
find . -name lds\* -mtime $X \
-exec rm -fR {} \;
As well as I've to delete the files from another FTP server which are again older than X... (0 Replies)
Hi,
I have a directory which contains files.This Directory keeps getting in new files from time to time.I want to maintain only 15 files in that directory at any time and the old files should be deleted.
Eg:
Directory 'c' @'a/b/c contains:
1_a
2_a
3_a...
I want to delete all the old... (2 Replies)
OK, Easy question probably, I have a directory that is full of like 1000 files.
I want to get rid of files more than 5 days old.
Is there an easy way to do this? there are like 800 files that fit into this category so doing it manually would be a pain.
Any help is appreciated! (1 Reply)
Hi Friends,
I am new to this , I am working on AIX system and my scenario is to retrive the files from remote system and remove the files from the remote system after retreving files. I can able to retrieve the files but Can't remove files in remote system. Please check my code and help me out... (3 Replies)
I'm baffled..... the system I work on creates files every Mon-Friday
I'm trying to delete all files older than 30 days old from a Unix prompt, the command I'm using is:
find /directory/ -mtime +30 -exec rm {} \;
however it returns /directory/filename: 644 mode ? (y/n) for every file! ... (1 Reply)
Hi
I have a file:
r58778.3|SOURCES={KEY=f665931a...,fw,221-705}|ERRORS={16_1:T,30_1:T,56_1:C,57_1:T,59_1:A,101_1:A,115:-,158_1:C,186_1:A,204:-,271_1:T,305:-,350_1:C,368_1:G,442_1:C,472_1:G,477_1:A}|SOURCE_1="Contig_1092402550638"(f665931a359e36cea0976db191ff60ff09cc816e)
I want to retain... (15 Replies)
#!/bin/bash
#
name=$1
type=$2
number=1
for file in ./**
do
if
then
filenumber=00$number
elif
then
filenumber=0$number
fi
tempname="$name""$filenumber"."$type"
if (4 Replies)
Hi
I have an AIX server. I'm planning to use the below script to remove 60 days older files.
find /path/ -mtime +60 -exec rm -f {} \;
I just want to make sure it will only remove the files. I don't want the directories to be removed.
If in case it will delete the directories... (2 Replies)
Discussion started by: newtoaixos
2 Replies
LEARN ABOUT DEBIAN
bup-margin
bup-margin(1) General Commands Manual bup-margin(1)NAME
bup-margin - figure out your deduplication safety margin
SYNOPSIS
bup margin [options...]
DESCRIPTION
bup margin iterates through all objects in your bup repository, calculating the largest number of prefix bits shared between any two
entries. This number, n, identifies the longest subset of SHA-1 you could use and still encounter a collision between your object ids.
For example, one system that was tested had a collection of 11 million objects (70 GB), and bup margin returned 45. That means a 46-bit
hash would be sufficient to avoid all collisions among that set of objects; each object in that repository could be uniquely identified by
its first 46 bits.
The number of bits needed seems to increase by about 1 or 2 for every doubling of the number of objects. Since SHA-1 hashes have 160 bits,
that leaves 115 bits of margin. Of course, because SHA-1 hashes are essentially random, it's theoretically possible to use many more bits
with far fewer objects.
If you're paranoid about the possibility of SHA-1 collisions, you can monitor your repository by running bup margin occasionally to see if
you're getting dangerously close to 160 bits.
OPTIONS --predict
Guess the offset into each index file where a particular object will appear, and report the maximum deviation of the correct answer
from the guess. This is potentially useful for tuning an interpolation search algorithm.
--ignore-midx
don't use .midx files, use only .idx files. This is only really useful when used with --predict.
EXAMPLE
$ bup margin
Reading indexes: 100.00% (1612581/1612581), done.
40
40 matching prefix bits
1.94 bits per doubling
120 bits (61.86 doublings) remaining
4.19338e+18 times larger is possible
Everyone on earth could have 625878182 data sets
like yours, all in one repository, and we would
expect 1 object collision.
$ bup margin --predict
PackIdxList: using 1 index.
Reading indexes: 100.00% (1612581/1612581), done.
915 of 1612581 (0.057%)
SEE ALSO bup-midx(1), bup-save(1)BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown-bup-margin(1)