Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • I don't have the source, I'm just using the cp that's installed on the system. Commented Dec 17, 2018 at 18:32
  • Sorry, I did not see that, but cp mmap()s larger parts of the input file before it calls write(). Is there anything with the input file? Commented Dec 17, 2018 at 18:43
  • I'm not sure, that file is one that was just created by the bamboo plan, I don't know of anything 'unusual' about it. Commented Dec 17, 2018 at 18:45
  • Then you could have a look at the OpenSolaris sources and look for related EACCESS returns. ACLs are e.g. such a case where a file access could cause EACCESS. Commented Dec 18, 2018 at 10:47
  • ACLs are e.g. such a case where a file access could cause EACCESS. I'm pretty sure the only way ACLs can cause an EACCESS return is on open() or openat(), although I haven't examined the kernel source. There's no way I can see for ACLs to cause a write() to return EACCESS, especially after a series of successful write() calls on that same file descriptor. Barring something on the NFS server (quite possible, and that's still a complete unknown...), the only way I see in the OpenSolaris source for write() to fail on EACCESS is for it to run into a file lock. Commented Dec 19, 2018 at 10:27