pthread_mutex_unlock(3t) [hpux man page]

pthread_mutex_unlock(3T)												  pthread_mutex_unlock(3T)

NAME

       pthread_mutex_unlock() - unlock a mutex.

SYNOPSIS

PARAMETERS

	      mutex	Pointer to the mutex to be unlocked.

DESCRIPTION

       The  function  is  called  by  the owner of the mutex referenced by mutex to unlock the mutex.  The manner in that the mutex is released is
       dependent upon the mutex's type attribute.  For normal and default mutexes, undefined behavior will result if  is  called  on  an  unlocked
       mutex  or  by  a  thread  that is not the current owner.  For recursive and error-checking mutexes, an error is returned if is called on an
       unlocked mutex or by a thread which is not the current owner.

       For recursive mutexes, the owner must call as many times as the mutex was locked before another thread can lock the mutex.

       If there are threads blocked on the mutex referenced by mutex when releases the mutex, the scheduling policy is	used  to  determine  which
       thread will acquire the mutex next.

RETURN VALUE

       Upon successful completion, returns zero. Otherwise, an error number is returned to indicate the error (the variable is not set).

ERRORS

       For each of the following conditions, if the condition is detected, the function returns the corresponding error number:

	      [EINVAL]	     mutex is not an initialized mutex.

	      [EPERM]	     The calling thread does not own mutex.  On HP-UX, this error is not detected for or mutexes.

	      [EFAULT]	     mutex parameter points to an illegal address.

AUTHOR

       was derived from the IEEE POSIX P1003.1c standard and HP extensions.

SEE ALSO

       pthread_mutex_init(3T), pthread_mutex_destroy(3T), pthread_mutex_lock(3T), pthread_mutex_trylock(3T).

STANDARDS CONFORMANCE

								  Pthread Library					  pthread_mutex_unlock(3T)

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)