You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If lapply is targeting an APFS-formatted volume, any applefiles that have resource forks will fail to be created. The error is:
filename.radmind.321/..namedfork/rsrc: No such file or directory
This is because on APFS volumes, the "..namedfork/rsrc" path is not available unless the file in question already has a resource fork attached. I've submitted a pull request with a patch for retr.c that fixes this.
The text was updated successfully, but these errors were encountered:
I realize this is fixed, but I suspect one reason why this was failing was that the O_CREAT and O_EXCL flags were not being passed when opening the resource fork. I just had added resource fork support to another project using the /..namedfork/rsrc path trick, and it did not require a call to setxattr() to create new resource forks.
If lapply is targeting an APFS-formatted volume, any applefiles that have resource forks will fail to be created. The error is:
filename.radmind.321/..namedfork/rsrc: No such file or directory
This is because on APFS volumes, the "..namedfork/rsrc" path is not available unless the file in question already has a resource fork attached. I've submitted a pull request with a patch for retr.c that fixes this.
The text was updated successfully, but these errors were encountered: