![]() ![]() -help: Standard, present on numerous tools.I suppose it might be useful, but probably only under specialized circumstances usually when you have a list of files, you want to operate on them all independently. -d/ -depth: This just reorders the output.If you're building find commands large and complex enough to require this, I don't want to work where you work. This specifies how find should optimize queries. -Olevel: This is completely ridiculous.But I do think it's a little silly that a file-listing tool needs this kind of thing. -D: Not intended for general use, so I'll let it slide.-P/ -L/ -H: This is present on numerous tools and is unsurprisingly also useful on find.OK, I'll use this man page for reference: There is literally no need for nearly all of find's features.Įdit: p.s I didn't downvote you though I do disagree with you completely.īut everything else specifies parameters to a search. exec is often far safer than a less experienced scripter use its output. But all you'd be doing is putting find's output into something else that can have word splitting issues. ![]() I should sit down and write a perl script to examine each file and see if it matches those parameters? The above is very similar to something I have had to search for this week alone.Ībout the only place I can see an arguement for here, is -exec - which could be argued to be doing what pipes/shellscript should. I need to find all non-zero sized files owned by uid 50 or gid 100 that have group execute permissions and haven't been modified in the last 30 days. It also doesn't support a fraction of the kinds of search parameters I'd expect out of a search tool. ![]() Locate is not a live search and so useless in the kinds of environments I work in. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |