[Previous] [Contents] [Next]

iofunc_rename()

Do permission checks for the _IO_CONNECT message

Synopsis:

#include <sys/iofunc.h>

int iofunc_rename( resmgr_context_t* ctp,
                   io_rename_t* msg,
                   iofunc_attr_t* oldattr,
                   iofunc_attr_t* olddattr,
                   iofunc_attr_t* newattr,
                   iofunc_attr_t* newdattr,
                   struct _client_info* info );

Library:

libc

Description:

The function iofunc_rename() does permission checks for the _IO_CONNECT message (subtype _IO_CONNECT_RENAME) for context ctp. The newattr argument is the attribute of the target if it already exists. The function is similar to the iofunc_open() function:

The iofunc_rename() function checks to see if the client (described by the optional info structure) has access to open the resource (name passed in the msg structure). The attr structure describes the resource's attributes.

The info argument can be passed as NULL, in which case iofunc_rename() obtains the client information itself via a call to iofunc_client_info(). It is, of course, more efficient to get the client information once, rather than call this function with NULL every time.

Returns:

EACCES
The client doesn't have permissions to do the operation.
EBADFSYS
NULL was passed in oldattr, olddattr, or newdattr.
EFAULT
A fault occurred when the kernel tried to access the info buffer.
EINVAL
The oldattr and newdattr have identical values, the client process is no longer valid, or attempt to remove the parent (".") directory.
EISDIR
The old link is a directory but the new link isn't a directory.
ENOTDIR
Attempt to unlink a nondirectory entry using directory semantics (e.g. rmdir file).
ENOTEMPTY
Attempt to remove a directory that isn't empty.
EOK
Successful completion or there was already a newattr entry.
EPERM
The group ID or owner ID didn't match.
EROFS
Attempt to remove an entry on a read-only filesystem.

Classification:

QNX 6

Safety:
Cancellation point No
Interrupt handler No
Signal handler Yes
Thread Yes

See also:

iofunc_client_info(), iofunc_open()


[Previous] [Contents] [Next]