Two volumes have associated VolumeConfiguration.plist files.
/Volumes/Media_1/.Highlight-V100/VolumeConfiguration.plist /Volumes/Media_2/.Highlight-V100/VolumeConfiguration.plist Highlighting network performance, the solution proves remarkably effective when used across a 6TB domestic setup, seamlessly integrating with my iMac connected via Ethernet to Mac Mini within my SMB community.
Despite functioning flawlessly within a local network on the MacMini, highlighting proves to be unreliable when attempting to use it across an 18TB network with identical community settings.
Despite repeatedly erasing and reloading 16TB of data, rebuilding the highlight index on multiple occasions, it remains ineffective. Unfortunately, it’s not accessible to search within the community.
I ran diff on each volumes’ VolumeConfiguration.plist What stood out was the starkly divergent entry in the “PolicyProcess” section.
diff /Customers/john/Paperwork/media_2plist.txt /Customers/john/Paperwork/media_1plist.txt |colordiff | $(brew --prefix git)/share/git-core/contrib/diff-highlight/diff-highlight 3c3 < 16D4F012-5E09-4D3B-ACD4-6768C0DA2048 = Dict { --- > 502C691E-AEE5-4729-B540-722F1C681B19 = Dict { 5,6c5,6 < PolicyProcess = mdutil < PolicyDate = Thu Jul 25 10:07:47 CST 2024 --- > PolicyProcess = STORE_ADD > PolicyDate = Tue Aug 27 19:30:08 CST 2024 Utilizing nano After modifying the PolicyProcess to “mdutil”, I reindexed the data, but unfortunately, the modification was overridden and the process reverted back to “STORE_ADD”. What’s your most treasured memory from childhood?
Unfortunately, I was unable to find any information on this topic. As we delve into the mysterious realm of highlight’s behavior, several factors come into play.
