Home
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
Programming
Writing a Resource Manager
Handling Other Messages
Your resource manager will likely need to handle messages for operations other than read and write. Here, we explain and demonstrate how to handle other common message types.
Handling lseek()

QNX Momentics IDE User's Guide
This User's Guide describes version 8.0 of the Integrated Development Environment (IDE) that's part of the QNX Tool Suite.
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
- Quickstart Guide
- System Architecture
  The System Architecture guide accompanies the QNX OS and is intended for both application developers and end-users.
- OS Components & Operations
- Graphics
- Programming
  - Getting Started with the QNX OS
    Getting Started with the QNX OS: A Guide for Realtime Programmers is intended to introduce you to the QNX OS and help you develop applications and resource managers for it.
  - Programmer's Guide
    The QNX OS Programmer's Guide covers a variety of topics that might interest developers who are building applications that will run under the QNX OS.
  - Writing a Resource Manager
    - What Is a Resource Manager?
      In general terms, a resource manager is a process that registers a pathname in the filesystem namespace. Other processes use that pathname to communicate with the resource manager.
    - The Bones of a Resource Manager
      Let's start with the overall structure of a resource manager. First we'll look at what happens under the covers on both the client side and the server side. After that, we'll go into the layers in a resource manager and then look at some examples.
    - Fleshing Out the Skeleton
      It's time now to start adding some flesh to the basic bones of the resource manager. We'll look at the types of messages you might have to handle, how to set the resource manager's attributes, how to add functionality, and some security issues you should consider.
    - POSIX-Layer Data Structures
      The resource manager library defines (in <sys/iofunc.h>) several key structures that are related to the POSIX-layer support routines.
    - Handling Read and Write Messages
      A resource manager must define routines or handlers to process requests by the client to receive data (read) or send data to the underlying device (write). Here, we give detailed examples of such handlers.
    - Resource Managers that Handle Multiple Devices
      Resource managers can easily be adapted to handle multiple devices.
    - Combine Messages
      To conserve bandwidth and to support atomic operations, combine messages are supported. A combine message is constructed by the client's C library and consists of multiple I/O and/or connect messages packaged together into one.
    - Using the Receive Buffer as a Reply Buffer
      When building a response to a client request, you often need a temporary buffer in which to build this response.
    - Handling Other Messages
      Your resource manager will likely need to handle messages for operations other than read and write. Here, we explain and demonstrate how to handle other common message types.
    - Unblocking Clients and Handling Interrupts
      Your resource manager needs to avoid leaving clients blocked indefinitely, and it might need to handle interrupts.
    - Multithreaded Resource Managers
      When you create a multithreaded resource manager, you should design it so that there's always at least one RECEIVE-blocked thread.
    - Filesystem Resource Managers
      Some resource managers need to implement filesystems by responding to access requests for any pathname within a directory structure.
    - Glossary
- System Security Guide
  The QNX System Security Guide is intended for both system integrators who are responsible for the security of a QNX OS system and developers who want to create a QNX OS resource manager free from vulnerabilities.
- Utilities & Libraries
- Migrating to QNX OS 8.0
QNX Software in the Cloud
QNX Software in the Cloud enables developers to use the QNX OS in the Amazon cloud environment.
QNX Toolkit for Visual Studio Code
This User's Guide describes the QNX^® Toolkit for Visual Studio Code. The guide introduces you to the QNX Toolkit by explaining the QNX development environment and how to build, run, and debug your QNX^® Operating System (OS) applications and systems.
QNX Hypervisor User's Guide
This User's Guide explains the QNX hypervisor architecture and provides instructions for installing and running a QNX Hypervisor system, changing system components and configuration, and using hypervisor features such as virtual devices (vdevs).
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation, explains how to obtain technical support, and provides some information about licensing.

Handling lseek()

QNX SDP8.0Writing a Resource ManagerDeveloper

Your resource manager will receive an _IO_LSEEK message when a client calls lseek(), fseek(), or rewinddir().

Note:

A resource manager that handles directories will also need to interpret the _IO_LSEEK message for directory operations.

The prototype for the io_lseek handler is as follows:

int io_lseek ( resmgr_context_t *ctp,
               io_lseek_t *msg,
               RESMGR_OCB_T *ocb )

The default handler, iofunc_lseek_default(), simply calls the iofunc_lseek() helper function.

The io_lseek_t structure is (once again), a union of an input message and an output message:

struct _io_lseek {
  uint16_t         type;
  uint16_t         combine_len;
  short            whence;
  uint16_t         flags;
  uint64_t         offset;
};

typedef union {
  struct _io_lseek i;
  uint64_t         o;
} io_lseek_t;

The whence and offset members of the input message are passed from the client's lseek() function. Usually, the routine should adjust the OCB's offset parameter after interpreting the whence and offset parameters. Then, it should return either the new offset in the reply message (for example, using the msg->o field) or an error.

The only currently defined flag is _IO_LSEEK_IGNORE_NON_SEEKABLE. The client sets this flag if it wants the resource manager to ignore the request if lseek operations aren't supported (for example, an aio_read() on a pipe). In this case, the resource manager shouldn't change the offset.

If the _IO_COMBINE_FLAG is set in the combine_len field, the message is part of a combine message. In this case, the handler should just return an error status on failure or EOK on success, and not return the current offset in the reply message.

Page updated: March 05, 2025