QNX Developer Support
|This version of this document is no longer maintained. For the latest documentation, see http://www.qnx.com/developers/docs.|
Create or access a named semaphore
#include <semaphore.h> sem_t * sem_open( const char * sem_name, int oflags, ... );
- The name of the semaphore that you want to create or access; see below.
- Flags that affect how the function creates a new semaphore.
This argument is a combination of:
Don't set oflags to O_RDONLY, O_RDWR, or O_WRONLY. A semaphore's behavior is undefined with these flags. The QNX libraries silently ignore these options, but they may reduce your code's portability.
For more information, see below.
If you set O_CREAT in oflags, you must also pass the following arguments:
- mode_t mode
- The semaphore's mode (just like file modes).
For portability, you should set the read, write,
and execute bits to the same value.
An easy way of doing this is to use the constants from
- S_IRWXG for group access.
- S_IRWXO for other's access.
- S_IRWXU for your own access.
For more information, see "Access permissions" in the documentation for stat().
- unsigned int value
- The initial value of the semaphore. A positive value (i.e. greater than zero) indicates an unlocked semaphore, and a value of 0 (zero) indicates a locked semaphore. This value must not exceed SEM_VALUE_MAX.
Use the -l c option to qcc to link against this library. This library is usually included automatically.
The sem_open() function creates or accesses a named semaphore. Named semaphores are slower than the unnamed semaphores created with sem_init(). Semaphores persist as long as the system is up.
|If you want to use named semaphores, the named-semaphore manager must be running. Starting with release 6.3.0, procnto, manages named semaphores, which mqueue used to do (and still does, if it detects that procnto isn't doing so).|
The sem_name argument is interpreted as follows:
|name||Pathname space entry|
where CWD is the current working directory for the program at the point that it calls sem_open().
|If you want to create or access a semaphore on another node, you have to specify the name as /net/node/sem_location.|
The oflags argument is used only for semaphore creation. When creating a new semaphore, you can set oflags to O_CREAT or (O_CREAT|O_EXCL):
- Create a new named semaphore. If you set this bit, you must provide the mode and value arguments to sem_open().
- When creating a new named semaphore, O_EXCL causes sem_open() to fail if a semaphore with sem_name already exists. Without O_EXCL, sem_open() attaches to an existing semaphore or creates a new one if sem_name doesn't exist.
|Don't mix named semaphore operations (sem_open() and sem_close()) with unnamed semaphore operations (sem_init() and sem_destroy()) on the same semaphore.|
A pointer to the created or accessed semaphore, or -1 for failure (errno is set).
- Either the named semaphore exists and you don't have permission to access it, or you're trying to create a new semaphore and you don't have permission.
- You specified O_CREAT and O_EXCL in oflags, but the semaphore already exists.
- The sem_name argument is invalid or, when creating a semaphore, value is greater than SEM_VALUE_MAX.
- The call was interrupted by a signal.
- Too many levels of symbolic links or prefixes.
- The process is using too many files or semaphores.
- The system ran out of resources and couldn't open the semaphore.
- The sem_name argument is longer than (NAME_MAX - 8).
- Either the manager for named semaphores (mqueue, if procnto isn't managing them) isn't running, or the sem_name argument doesn't exist and you didn't specify O_CREAT in oflags.
- There's insufficient space to create a new named semaphore.
- The sem_open() function isn't implemented for the filesystem specified in sem_name.