Default unblock handler


#include <sys/iofunc.h>

int iofunc_unblock_default( resmgr_context_t * ctp,
                            io_pulse_t * msg,
                            iofunc_ocb_t * ocb );


BlackBerry 10.0.0


A pointer to a resmgr_context_t structure that the resource-manager library uses to pass context information between functions.
A pointer to the io_pulse_t structure that describes the pulse that the resource manager received.
A pointer to the iofunc_ocb_t structure for the Open Control Block that was created when the client opened the resource.



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


The iofunc_unblock_default() function calls iofunc_unblock().

The iofunc_unblock_default() function implements the functionality required when the client requests to be unblocked (e.g. a signal or timeout).

If your resource manager uses iofunc_lock_default(), you must use both iofunc_unblock_default() and iofunc_close_dup_default() in their respective handlers, as they provide necessary ancillary functionality for managing file locks. This is because file locks are owned by the process, and aren't inherited by the child process.

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

The unblock message is synthesized by the resource-manager shared library when a client wishes to unblock from its MsgSendv() to the resource manager. The iofunc_unblock_default() function takes care of freeing up any locks that the client may have placed on the resource.


No client connection was found.
A client connection has been unblocked.


If your lock handler called iofunc_lock_default(), your unblock handler must call iofunc_unblock_default():

int my_unblock_handler (resmgr_context_t *ctp, io_pulse_t *msg, RESMGR_OCB_T *ocb)
   int status;

   if((status = iofunc_unblock_default(...)) != _RESMGR_DEFAULT)
      return status;

   /* Do any additional work required to look for a client to unblock. */


QNX Neutrino

Cancellation point No
Interrupt handler No
Signal handler Yes
Thread Yes

Last modified: 2014-06-24

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

comments powered by Disqus