New -find test -size
This commit is contained in:
@ -50,7 +50,7 @@
|
||||
@c man .\" First parameter, NAME, should be all caps
|
||||
@c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
|
||||
@c man .\" other parameters are allowed: see man(7), man(1)
|
||||
@c man .TH XORRISO 1 "Version 1.5.5, Oct 06, 2022"
|
||||
@c man .TH XORRISO 1 "Version 1.5.5, Nov 09, 2022"
|
||||
@c man .\" Please adjust this date whenever revising the manpage.
|
||||
@c man .\"
|
||||
@c man .\" Some roff macros, for reference:
|
||||
@ -2429,6 +2429,33 @@ and "Xotic" which matches what is not matched by the other types.
|
||||
@*
|
||||
Only the first letter is interpreted. E.g.: -find / -type d
|
||||
@*
|
||||
@item -size [+-][=]number[cwbdksmg] :
|
||||
Matches files with matching relation to the given size number.
|
||||
@*
|
||||
The prefix defines the desired relation:
|
||||
@*
|
||||
No prefix or prefix "=" means: File must have exactly the given size.
|
||||
@*
|
||||
Prefix "+" means: File must be larger than given size.
|
||||
@*
|
||||
Prefix "+=" means: File must be larger than or equal to given size limit.
|
||||
@*
|
||||
Prefix "-" means: File must be smaller than given size limit.
|
||||
@*
|
||||
Prefix "-=" means: File must be smaller than or equal to given size limit.
|
||||
@*
|
||||
Suffixes are peculiar to stay compatible with program "find":
|
||||
@*
|
||||
No suffix means blocks of 512 bytes, "c" means single bytes, "w" means 2 bytes,
|
||||
"b" means 512 bytes.
|
||||
The suffixes "k", "M", and "G" mean 1024, 1024k, and 1024M respectively.
|
||||
As usual with xorriso, the suffixes "d" and "s" mean 512 and 2048 and all
|
||||
suffixes are recognized as both, uppercase and lowercase letters.
|
||||
@*
|
||||
E.g. match files of 4 GiB or larger:
|
||||
@*
|
||||
-size +=4g
|
||||
@*
|
||||
@item -maxdepth number :
|
||||
Matches only files which are at most at the given depth level relative to
|
||||
the iso_rr_path where -find starts. That path itself is at depth 0, its
|
||||
|
Reference in New Issue
Block a user