PTHREAD_RWLOCK_WRLOCK(3) BSD Programmer's Manual PTHREAD_RWLOCK_WRLOCK(3)
pthread_rwlock_wrlock, pthread_rwlock_trywrlock - acquire a read/write
lock for writing
#include <pthread.h>
int
pthread_rwlock_wrlock(pthread_rwlock_t *lock);
int
pthread_rwlock_trywrlock(pthread_rwlock_t *lock);
The pthread_rwlock_wrlock() function blocks until a write lock can be ac-
quired against lock. The pthread_rwlock_trywrlock() function performs the
same action, but does not block if the lock cannot be immediately ob-
tained.
The results are undefined if the calling thread already holds the lock at
the time the call is made.
To prevent writer starvation, writers are favored over readers.
If successful, the pthread_rwlock_wrlock() and pthread_rwlock_trywrlock()
functions will return zero. Otherwise an error number will be returned to
indicate the error.
The pthread_rwlock_trywrlock() function will fail if:
[EBUSY] The calling thread is not able to acquire the lock without
blocking.
The pthread_rwlock_wrlock() and pthread_rwlock_trywrlock() functions may
fail if:
[EDEADLK] The calling thread already owns the read/write lock (for
reading or writing).
[EINVAL] The value specified by lock is invalid.
[ENOMEM] Insufficient memory exists to initialize the lock (applies
to statically initialized locks only).
pthread_rwlock_unlock(3)
The pthread_rwlock_wrlock() and pthread_rwlock_trywrlock() functions are
expected to conform to Version 2 of the Single UNIX Specification.
The pthread_rwlock_wrlock() function first appeared in FreeBSD 3.0 and
OpenBSD 2.5.
MirOS BSD #10-current August 4, 1998 1
Generated on 2012-02-20 02:47:02 by $MirOS: src/scripts/roff2htm,v 1.70 2011/12/03 18:21:12 tg Exp $
These manual pages and other documentation are copyrighted by their respective writers;
their source is available at our CVSweb,
AnonCVS, and other mirrors. The rest is Copyright © 2002‒2011 The MirOS Project, Germany.
This product includes material
provided by Thorsten Glaser.
This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report – diffs preferred.