×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello Justin,
Am 20.05.2021 um 17:45 schrieb Justin Taylor <jtaylor.0ab@xxxxxxxxx>:
I have a rename() API call that's failing with "Operation not permitted.".
The user doing the rename isn't the owner but have *RWX / *ALL authority to
the IFS file.
In addition to what others said, allow me to clarify some UNIX concept about access rights.
Rights (r, w, x) always apply to the *content* of the object in question. So, if a user/group/other has write access to a file, he may change the *content* of the file.
This does *not* include deletion of the file! Why? If the user in question creates or deletes a file, or changes access rights, the user *changes a data structure in the parent directory* of the object. Thus, to create, or delete a file, the *parent directory has to allow write access*.
(This makes it easy to allow creation and deletion of files in a directory, but not to change these file's contents, if this is desired.)
The same goes for any combination of r, w, and x flags. x for a directory means: Allowance to set your current working directory there (cd /go/there/into). This enables some very interesting, but not too much relevant possibilities for actual real-world scenarios.
UNIX is very different there from other OS's, and very sparse compared to Novell Netware rights. I do not have enough first-hand experience with Windows, so I can't tell about that. Today, UNIX file systems are often accessed via Samba, which has the unthankful job to map the different Windows rights to some messy mix of UNIX rights, possibly plus ACLs — forcibly applied by Samba on the UNIX side of affairs.
:wq! PoC
midrange.com
