Sunday, October 6, 2024

community – What do the totally different Highlight PolicyProcess varieties: “mdutil” and “STORE_ADD” do?

I’ve two volumes each with VolumeConfiguration.plist information:

/Volumes/Media_1/.Highlight-V100/VolumeConfiguration.plist
/Volumes/Media_2/.Highlight-V100/VolumeConfiguration.plist

Highlight works very properly on 6TB Media_2 regionally and over my SMB community (iMac-ethernet-MacMini)

Highlight does not work correctly on 18TB Media_1 over the identical community, however works superb regionally (on the MacMini).

I’ve erased Media_1 and reloaded 16TB of information and rebuilt the highlight index quite a few occasions and it is no use. It isn’t searchable over the community.

I ran diff on each volumes’ VolumeConfiguration.plist and what jumped out was the totally different string in “PolicyProcess”:

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 I modified the PolicyProcess on Media_1 to “mdutil” after which rebuilt the index however it had been modified again to “STORE_ADD”. That is how Highlight needs/wants it.

I am unable to discover any documentation on this. Why Highlight is doing it, and many others.

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles