masc

I can confirm the time machine errors are (presumably) not caused by this, but rather...

https://sourceforge.net/p/netatalk/bugs/636/

dsi_stream_read: len:0, unexpected EOF remains unfixed

I wouldn't think so. why should utime be updated from spotlight metadata ever?

yes certainly. setting utime from md attributes or touching utime in general in this...

confirmed here as well under the same conditions. prio 1? this is filesystem metadata...

however, I just verified against 3.1.0.. and it works. great!

comment mentions, the fix relates to an issue occuring with "follow symlinks" enabled...