Page 1 of 1

Hazel + Linux Issue (Last Matched data lost on Linux reboot)

PostPosted: Tue Apr 24, 2018 9:42 am
by dudeslife
I have Hazel running on my Mac with rules set for a Linux volume on my network. It runs well except for the Last Matched info seems to get lost when I reboot the Linux box. So it is digging into folders and trying to move files into that same folder.. Any ideas on how I can fix this. My Hazel log is full of the "destination is the same as source" errors. Thanks for any help.

Re: Hazel + Linux Issue (Last Matched data lost on Linux reb

PostPosted: Tue Apr 24, 2018 12:20 pm
by Mr_Noodle
That's odd since last matched is not stored with the destination folder. I'm wondering if the linux volume doesn't provide a stable unique identifier to macOS, thus making Hazel think that the destination is a new volume. Can you provide an excerpt from the logs?

Re: Hazel + Linux Issue (Last Matched data lost on Linux reb

PostPosted: Sun Apr 29, 2018 7:20 pm
by dudeslife
Mr_Noodle wrote:That's odd since last matched is not stored with the destination folder. I'm wondering if the linux volume doesn't provide a stable unique identifier to macOS, thus making Hazel think that the destination is a new volume. Can you provide an excerpt from the logs?


I added a parameter so Hazel will ignore any file not created in the last 2 minutes. That solved my problem of reprocessing attempts.