FIND-FILTER(1)
π FIND-FILTER(1) π
okay bestie, welcome to the fine-grained file selection page β this is find-filter from the Performance Co-Pilot manual, and honestly? it's giving "tiny tool, huge main character energy" π
β¨ NAME β¨
find-filter β fine-grained file selection based on time attributes πΈ
π¦ SYNOPSIS π¦
$PCP_BINADM_DIR/find-filter [-v?] predicate
π DESCRIPTION π
so like. find-filter is a filter for a list of file names read on standard input, and if the files match the predicate, their names get written on standard output. that's it, that's the vibe π
The supported predicate forms are based on the file's creation time or modification time, and take the form ctime or mtime followed by a time specification. A time specification takes the form of a + or - followed by days (a non-negative integer), optionally followed by a colon (:) and hours (an integer in the range 0 to 23), optionally followed by another colon (:) and minutes (an integer in the range 0 to 59). π°οΈ
The semantics of the time specification are that a file matches the predicate if the chosen time attribute for the file is less than (+) the current time minus the time specification, else more than or equal to (-) the current time minus the time specification. Alternatively, + means before the current time minus the time specification, and - means at or after the current time minus the time specification. no cap, that's literally the whole logic π§ β¨
find-filter is intended to be used to provide finer-grain and platform independent selection compared to the -mtime or -ctime options of find(1). find-filter is expected to be used as a post-filter for the output from find(1), and this is how it is used in the pmlogger_daily(1) scripts to select files to be compressed or culled. iconic behaviour honestly π
π EXAMPLES π
The following predicate examples illustrate some typical uses. π
mtime +3β Matches files modified more than3days ago.ctime -0:2β Matches files created in the last2hours.ctime +0:0:15β Matches files created more than15minutes ago.
π DIAGNOSTICS π
There are none, unless the -v option is used, in which case some diagnostics are written to standard error. π
Exit status is always zero, unless there are errors found when parsing the command line arguments. periodt. π
π SEE ALSO π
find(1) and pmlogger_daily(1). go read those too bestie, iykyk πβ¨
ok that's the whole page, you ate that π«Ά go filter some files and slay π
mwah π β this was the FIND-FILTER(1) page from Performance Co-Pilot (PCP), General Commands Manual, and that's the tea π
π¦ where this page comes from
- arch rolling: pcp 7.2.2-2 Β· GPL-2.0-or-later AND LGPL-2.1-or-later AND CC-BY-3.0
- centos-stream 10: pcp-doc 7.1.5-6.el10 Β· GPL-2.0-or-later AND CC-BY-3.0
- centos-stream 9: pcp-doc 6.3.7-14.el9 Β· GPL-2.0-or-later AND CC-BY-3.0
- debian trixie: pcp 6.3.8-1
- fedora 43: pcp-doc 7.0.1-1.fc43 Β· GPL-2.0-or-later AND CC-BY-3.0
- fedora 43: pcp-doc 7.2.1-1.fc43
- fedora 43: pcp-doc 7.2.2-1.fc43
- fedora 43: pcp-doc 7.2.2-2.fc43 Β· GPL-2.0-or-later AND CC-BY-3.0
- fedora 44: pcp-doc 7.1.0-6.fc44 Β· GPL-2.0-or-later AND CC-BY-3.0
- fedora 44: pcp-doc 7.2.1-1.fc44
- fedora 44: pcp-doc 7.2.2-1.fc44
- fedora 44: pcp-doc 7.2.2-2.fc44 Β· GPL-2.0-or-later AND CC-BY-3.0
- ubuntu questing: pcp 6.3.8-1
- ubuntu resolute: pcp 7.1.1-1
- ubuntu stonking: pcp 7.2.1-2build1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms