[basex-talk] ignoring macos turds via webdav

Finder and /bin/cp leave turds wherever they go in some situations.

If I use finder or cp in macos to write a file to a basex db mounted via webdav, the log shows something like:

[propfind ] …/a.xml [put] …/a.xml [propfind] …/._a.xml [lock] .../a.xml [propfind] .../a.xml [propfind] …/._. [propfind] …/

Then finder complains “some data could not be read or written”, or cp complains “interrupted system call”.

I imagine some sort of intermediate between Milton and basex could respond in a way that ignores the turds and responds as expected to macos.

Assuming that it is the turds that are causing the problem, do you know of an existing server-side solution?

Kendall