Opened 5 days ago
Last modified 31 minutes ago
#73455 assigned defect
findutils: cannot use locate; updatedb apparently fails to do anything useful!
| Reported by: | seamusdemora (Seamus) | Owned by: | mascguy (Christopher Nielsen) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.11.6 |
| Keywords: | sequoia | Cc: | |
| Port: | findutils |
Description (last modified by seamusdemora (Seamus))
I've just installed 'findutils' to help me verify the location of files I've installed with macPorts. Unfortunately, while I manually tracked the file ('libaacs.a') down (in '/opt/local/lib'), "locate" refuses to find anything.
"updatedb" reports the following gibberish:
sudo /opt/local/libexec/gnubin/updatedb gfind: '/Library/Caches/com.apple.amsengagementd.classicdatavault': Operation not permitted gfind: '/Library/Caches/com.apple.aneuserd': Operation not permitted gfind: '/Library/Caches/com.apple.aned': Operation not permitted gfind: '/System/Library/AssetsV2/com_apple_MobileAsset_UAF_FM_Overrides': Operation not permitted gfind: '/System/Volumes/Data/Library/Caches/com.apple.amsengagementd.classicdatavault': Operation not permitted gfind: '/System/Volumes/Data/Library/Caches/com.apple.aneuserd': Operation not permitted gfind: '/System/Volumes/Data/Library/Caches/com.apple.aned': Operation not permitted gfind: failed to read file names from file system at or below '/': No such file or directory
What must I do to get "locate" to work, and "updatedb" to index my filesystem properly??
I've read 'man updatedb', but it provided no insight for me. One thing that's particularly confusing is the location of the database. 'man updatedb' says, "... the default is /var/cache/locate/locatedb", but that doesn't exist on my system. I've also read some stuff in StackExchange suggesting that the problem may be Apple's native 'locate' and its database getting mixed up with the GNU/MacPorts version of 'locate' and its database.
Apologies if this seems like a lame request... I've tried to find a solution, but come up empty-handed! And PLEASE let me know if additional details are needed.
Change History (4)
comment:1 Changed 4 days ago by seamusdemora (Seamus)
| Description: | modified (diff) |
|---|
comment:2 Changed 4 days ago by ryandesign (Ryan Carsten Schmidt)
| Keywords: | sequoia added |
|---|---|
| Owner: | set to mascguy |
| Port: | findutils added |
| Status: | new → assigned |
| Summary: | macOS sequoia cannot use locate; updatedb apparently fails to do anything useful! → findutils: cannot use locate; updatedb apparently fails to do anything useful! |
| Type: | request → defect |
comment:3 Changed 4 days ago by seamusdemora (Seamus)
| Description: | modified (diff) |
|---|

Some added information: This is not the Mac I ordinarily use - it belongs to my wifey-poo :) She apparently recently upgraded the OS from "whatever" to Sequoia. I installed MacPorts on this machine when it was still running the "whatever" version of the OS :(
After re-reading some of the documentation, I have noted that either a "migration" or an "un-install" are recommended (required?) for MacPorts when upgrading the OS; further, the "migration" option must apparently be done BEFORE the OS upgrade. IOW - the failure I've reported could be entirely down to my lack of awareness!
However: On my Mac (Ventura OS) I seem to have exactly the same issue with the GNU version of 'locate' - also installed through MacPorts. This is particularly problematic for me because the "native"/Apple-supplied version of 'locate' also has issues that have effectively rendered it useless for my needs.
All that said: I would truly appreciate some advice, or a recommended course of action, or a status update on this ticket from one of the maintainers. Again - I would love to "help", so please let me know if I can do anything at all to move this issue toward resolution.
Best Rgds, ~S