Timeline for How can I search 360,000 files, about 280 GB?
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 30, 2018 at 16:50 | comment | added | Natsfan | It sounds like your problem has been solved. I was going to suggest EasyFind because it has nice features to narrow your search but I guess it most likely uses 'find' and 'grep' as well. EasyFind is free at the MacApp Store. | |
| Jun 30, 2018 at 9:41 | answer | added | nohillside♦ | timeline score: 1 | |
| Jun 6, 2018 at 23:32 | comment | added | l008com | Seems to be working. I guess that stray -r was causing all of my problems! | |
| Jun 6, 2018 at 12:23 | comment | added | fd0 |
You should remove the -print primary from your find statement. It is just repeating the results of grep.
|
|
| Jun 6, 2018 at 12:09 | comment | added | l008com |
@NimeshNeema I gave Xcode a try but I know so little about it, I didn't get far. I did try dumping all the files in, but it was attempting to index them all. An index based search won't work for this because the type of content I'm looking for will most likely not get indexed, as they're not real 'words'. Plus I dropped 370,000 files in there but it was only scanning 30,000 of them. Clearly I'm way out of my element there, but hopefully this find/grep thing works.
|
|
| Jun 6, 2018 at 12:06 | comment | added | l008com | A few minutes didn't get any too-many-files errors. So I'm going to let the full shell script run while I sleep without the -r's. So I'll be back with a followup in about 12 or so hours... | |
| Jun 6, 2018 at 11:54 | comment | added | l008com |
@nohillside testing without the -r now, ill be kind of amazed if that's all it turns out to be. Also added -type f to the find command so it skips directories.
|
|
| Jun 6, 2018 at 11:53 | comment | added | nohillside♦ | @NimeshNeema Don't know how good Xcode works with binary files though | |
| Jun 6, 2018 at 11:33 | comment | added | Nimesh Neema♦ | May sound a bit counter-intuitive, but try by creating an Xcode project, add all the files and use Xcode's built in search. Apple has repeatedly claimed how Xcode text searching is multiple times faster compared to grep. Also, I am not sure and assuming that Xcode shouldn't hit problems that you have mentioned. | |
| Jun 6, 2018 at 11:33 | comment | added | nohillside♦ |
Ah, you don't need grep -r if you use find, otherwise you traverse the subdirectories twice (and get the error from zfgrep ).
|
|
| Jun 6, 2018 at 11:31 | comment | added | nohillside♦ |
grep is the way to go here. Are you sure grep is the issue here? What happens if you run find /... -print, does it run through or terminate as well? And you definitively shouldn't get too many open files if you use find ... -exec grep so can you please, for both commands, copy/paste directly from Terminal so we see what you see?
|
|
| Jun 6, 2018 at 11:22 | history | asked | l008com | CC BY-SA 4.0 |