Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

tis_mutex_trylock(3) [osf1 man page]

tis_mutex_trylock(3)					     Library Functions Manual					      tis_mutex_trylock(3)

NAME
tis_mutex_trylock - Attempts to lock the specified mutex. LIBRARY
Standard C Library (libc.so, libc.a) SYNOPSIS
#include <tis.h> int tis_mutex_trylock( pthread_mutex_t *mutex); STANDARDS
None PARAMETERS
Address of the mutex (passed by reference) to be locked. DESCRIPTION
This routine attempts to lock the specified mutex mutex. When this routine is called, an attempt is made immediately to lock the mutex. If the mutex is successfully locked, zero (0) is returned. If the specified mutex is already locked when this routine is called, the caller does not wait for the mutex to become available. [EBUSY] is returned, and the thread does not wait to acquire the lock. RETURN VALUES
If an error condition occurs, this routine returns an integer value indicating the type of error. Possible return values are as follows: Successful completion. The mutex is already locked; therefore, it was not acquired. The value specified by mutex is invalid. ERRORS
None RELATED INFORMATION
Functions: tis_mutex_destroy(3), tis_mutex_init(3), tis_mutex_lock(3), tis_mutex_unlock(3) Manuals: Guide to DECthreads and Programmer's Guide delim off tis_mutex_trylock(3)

Check Out this Related Man Page

pthread_mutex_unlock(3) 				     Library Functions Manual					   pthread_mutex_unlock(3)

NAME
pthread_mutex_unlock - Unlocks the specified mutex. LIBRARY
DECthreads POSIX 1003.1c Library (libpthread.so) SYNOPSIS
#include <pthread.h> int pthread_mutex_unlock( pthread_mutex_t *mutex); STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: IEEE Std 1003.1c-1995, POSIX System Application Program Interface PARAMETERS
Mutex to be unlocked. DESCRIPTION
This routine unlocks the mutex specified by the mutex argument. This routine behaves as follows, based on the type of the specified mutex: For a normal, default, or errorcheck mutex: if the mutex is owned by the calling thread, it is unlocked with no current owner. Further, for a normal or default mutex: if the mutex is not locked or is locked by another thread, this routine can also return [EPERM], but this is not guaranteed. For an errorcheck mutex: if the mutex is not locked or is locked by another thread, this routine returns [EPERM]. For a recursive mutex: if the mutex is owned by the calling thread, the lock count is decremented. The mutex remains locked and owned until the lock count reaches zero (0). When the lock count reaches zero, the mutex becomes unlocked with no current owner. If one or more threads are waiting to lock the specified mutex, and the mutex becomes unlocked, this routine causes one thread to unblock and to try to acquire the mutex. The scheduling policy is used to determine which thread to unblock. For the SCHED_FIFO and SCHED_RR policies, a blocked thread is chosen in priority order, using first-in/first-out within priorities. Note that the mutex might not be acquired by the awakened thread if any other running thread attempts to lock the mutex first. On Tru64 UNIX, if a signal is delivered to a thread waiting for a mutex, upon return from the signal handler, the thread resumes waiting for the mutex as if it was not interrupted. RETURN VALUES
If an error condition occurs, this routine returns an integer value indicating the type of error. Possible return values are as follows: Successful completion. The value specified for mutex is invalid. The calling thread does not own the mutex. ERRORS
None RELATED INFORMATION
Functions: pthread_mutexattr_settype(3), pthread_mutex_destroy(3), pthread_mutex_init(3), pthread_mutex_lock(3), pthread_mutex_trylock(3) Manuals: Guide to DECthreads and Programmer's Guide delim off pthread_mutex_unlock(3)
Man Page