| Main index | Section 3 | Options |
#include <pthread.h>
A thread may hold multiple concurrent read locks. The pthread_rwlock_unlock(3) function must be called once for each lock acquired.
If the thread should be interrupted by a signal, the pthread_rwlock_timedrdlock() function will be automatically restarted after the thread returns from the signal handler.
The calling thread may deadlock if at the time the call is made it holds a write lock on rwlock. The results are undefined if this function is called with an uninitialized read-write lock.
This function shall not return an error code of EINTR.
| [ETIMEDOUT] | |
| The lock could not be acquired before the specified timeout expired. | |
The pthread_rwlock_timedrdlock() function may fail if:
| [EAGAIN] | |
| The read lock could not be acquired because the maximum number of read locks for rwlock would be exceeded. | |
| [EDEADLK] | |
| The calling thread already holds a write lock on rwlock. | |
| [EINVAL] | |
| The value specified by rwlock does not refer to an initialized read-write lock object, or the abs_timeout nanosecond value is less than zero or greater than or equal to 1 billion. | |
| PTHREAD_RWLOCK_TIMEDRDLOCK (3) | August 17, 2018 |
| Main index | Section 3 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
| “ | Modern Unix impedes progress in computer science, wastes billions of dollars, and destroys the common sense of many who seriously use it. | ” |
| — The Unix Haters' handbook | ||