I am trying to figure out the syntax to use find to remove files older than 30 minutes. I know that this will work for files 1 day old, but cannot seem to trim the time down to 30 minutes.
find /path/to/file -ctime +1 -exec rm -f {} \; (1 Reply)
Hi, I am using Solaris 5.8
I searched online, the find command has an option called maxdepth which can be used to limit the number of directories find will look into.
find . -maxdepth 2 -type f
When I run the above command in solaris, I get an error
find: bad option -maxdepth
find:... (2 Replies)
Hi
I wish to find only files in dir /srv/container/content/imz06/. It means exclude subfolder /srv/container/content/imz06/archive/
> uname -a
SunOS testbox6 5.10 Generic_139555-08 sun4v sparc SUNW,Sun-Blade-T6320Its Solaris default "find"
> find /srv/container/content/imz06/* -name... (4 Replies)
I know that find -ctime +1 will find ALL files that have been modified
that are greater than 1 day old and -ctime 1 will find files that are
ONLY 1 day old -ctime -1 mean files that are less than a day old?
Can find actually use this granularity? (5 Replies)
startdate="2012_07_04-16:14:4"
path1="/home/drdos/sample"
days=0
find $path1 -name "*$startdate*" > teste.txt
while
do
find $path1 -name "*.zip" ctime $days > teste.txt
days=`expr $days + 1`
done
echo " Files that are near the string u search are on teste.txt"Hi to... (2 Replies)
Can you please figure out what is the issue here
$ find . -maxdepth 1 -type f -size 0 -print
find: bad option -maxdepth
please find the OS details
$ uname -a
HP-UX g5u1216 B.11.31 U ia64 2614088426 unlimited-user license
Use code tags, thanks. (6 Replies)
When I use the command find "/abc/xyz" -type f -ctime +30 getting the error as
find:"/abc/xyz /lost+found: Permission Denied"
I tired find "/abc/xyz" -type d \( ! lost+found \) -type f -ctime +30 The error is
find: paths must precede expression Usage: find
Tried find "/abc/xyz"... (1 Reply)
The problem is this one. I tar and gzip files on remote server
Code:
find . -ctime -1 | tar -cvf transfer_dmz_start_daily.tar *${Today}*.*;
Command
Code:
find . -ctime -1
Doesn't find files without extension
Code:
.csv .txt
I have to collect all files for current... (1 Reply)
The problem is this one. I tar and gzip files on remote server
find . -ctime -1 | tar -cvf transfer_dmz_start_daily.tar *${Today}*.*;
Command
find . -ctime -1
Doesn't find files without extension
.csv .txt
I have to collect all files for current day, when the program... (1 Reply)
Discussion started by: digioleg54
1 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)