iofunc_utime_default()

Default handler for _IO_UTIME messages

Synopsis:

#include <sys/iofunc.h>

int iofunc_utime_default( resmgr_context_t* ctp,
                          io_utime_t* msg,
                          iofunc_ocb_t* ocb );

Since:

BlackBerry 10.0.0

Arguments:

ctp
A pointer to a resmgr_context_t structure that the resource-manager library uses to pass context information between functions.
msg
A pointer to the io_utime_t structure that contains the message that the resource manager received; see iofunc_utime().
ocb
A pointer to the iofunc_ocb_t structure for the Open Control Block that was created when the client opened the resource.

Library:

libc

Use the -l c option to qcc to link against this library. This library is usually included automatically.

Description:

The iofunc_utime_default() function implements POSIX semantics for the client's utime() call, which is received as an _IO_UTIME message by the resource manager.

You can place this function directly into the io_funcs table passed to resmgr_attach(), at the utime position, or you can call iofunc_func_init() to initialize all of the functions to their default values.

The iofunc_utime_default() function calls iofunc_utime() to do the actual work. It verifies that the client has the necessary permissions to effect a utime on the device. If so, the utime is performed, modifying elements of the ocb->attr structure. This function takes care of updating these bits in the flags member of ocb->attr:

  • IOFUNC_ATTR_ATIME
  • IOFUNC_ATTR_CTIME
  • IOFUNC_ATTR_MTIME
  • IOFUNC_ATTR_DIRTY_TIME
  • IOFUNC_ATTR_DIRTY_MODE

The iofunc_utime() function then calls iofunc_time_update() to update the appropriate time fields in ocb->attr.

Returns:

EOK
Successful completion.
EROFS
An attempt was made to utime a read-only filesystem.
EACCES
The client doesn't have permissions to do the operation.
EPERM
The group ID or owner ID didn't match.

Classification:

QNX Neutrino

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

Last modified: 2014-11-17



Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus