What do I do if I get OS_ERR_NOT_OWNER error code when using any OS Abstractor resources?

What do I do if I get OS_ERR_NOT_OWNER error code when using any OS Abstractor resources?

This error code indicates that the resource was created with a Process scope and only the process, which created this resource, can use it. If you need the resource to be shared across processes, then use OS_SCOPE_SYSTEM option during creation of system resources.


    • Related Articles

    • What do I do if I get OS_ERR_RESOURCE error code when creating the OS Abstractor resources?

      This error code indicates that the application is exceeding the max-allowed resources (see section Resource Configuration) and there are no free resource control blocks. To prevent this error from occurring, adjust max-allowed resource configuration ...

    • Why should I use OS Abstractor with my proprietary OS?

      Using OS Abstractor with your proprietary OS will give you the following benefits: Leverage re-usable open source POSIX/Linux code to efficiently add feature rich services in a cost-effective to your proprietary OS Make your application more ...

    • What is OS Abstractor and Cross OS Development Platform?

      Cross-OS Development Platform™ is a C/C++ source-level virtualization technology that provides a robust and industry standard OS interface architecture for flexible real-time application development, while allowing the user to protect the software ...

    • What is OS Abstractor and Cross OS Development Platform?

      Cross-OS Development Platform™ is a C/C++ source-level virtualization technology that provides a robust and industry standard OS interface architecture for flexible real-time application development, while allowing the user to protect the software ...

    • What is OS Abstractor and Cross OS Development Platform?

      Cross-OS Development Platform™ is a C/C++ source-level virtualization technology that provides a robust and industry standard OS interface architecture for flexible real-time application development, while allowing the user to protect the software ...