from small one page howto to huge articles all in one place
 

search text in:





Poll
What does your sytem tell when running "ulimit -u"?








poll results

Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

194569

userrating:

average rating: 1.7 (102 votes) (1=very good 6=terrible)


May 25th. 2007:
Words

486

Views

251893

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

140716

userrating:

average rating: 1.4 (42 votes) (1=very good 6=terrible)


April, 26th. 2006:

Druckversion
You are here: manpages





PTHREAD_MUTEX_CONSISTENT

Section: Linux Programmer's Manual (3)
Updated: 2017-08-20
Index Return to Main Contents
 

NAME

pthread_mutex_consistent - make a robust mutex consistent  

SYNOPSIS

#include <pthread.h>

int pthread_mutex_consistent(pthread_mutex_t *mutex);

Compile and link with -pthread.

Feature Test Macro Requirements for glibc (see feature_test_macros(7)):

pthread_mutex_consistent():

_POSIX_C_SOURCE >= 200809L
 

DESCRIPTION

This function makes a robust mutex consistent if it is in an inconsistent state. A mutex can be left in an inconsistent state if its owner terminates while holding the mutex, in which case the next owner who acquires the mutex will succeed and be notified by a return value of EOWNERDEAD from a call to pthread_mutex_lock().  

RETURN VALUE

On success, pthread_mutex_consistent() returns 0. Otherwise, it returns a positive error number to indicate the cause of the error.  

ERRORS

EINVAL
The mutex is either not robust or is not in an inconsistent state.
 

VERSIONS

pthread_mutex_consistent() was added to glibc in version 2.12.  

CONFORMING TO

POSIX.1-2008.  

NOTES

pthread_mutex_consistent() simply informs the implementation that the state (shared data) guarded by the mutex has been restored to a consistent state and that normal operations can now be performed with the mutex. It is the application's responsibility to ensure that the shared data has been restored to a consistent state before calling pthread_mutex_consistent().

Before the addition of pthread_mutex_consistent() to POSIX, glibc defined the following equivalent nonstandard function if _GNU_SOURCE was defined:

int pthread_mutex_consistent(const pthread_mutex_t *mutex);

This GNU-specific API, which first appeared in glibc 2.4, is nowadays obsolete and should not be used in new programs.  

EXAMPLE

See pthread_mutexattr_setrobust(3).  

SEE ALSO

pthread_mutexattr_init(3), pthread_mutex_lock(3), pthread_mutexattr_setrobust(3), pthread_mutexattr_getrobust(3), pthreads(7)  

COLOPHON

This page is part of release 4.13 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.


 

Index

NAME
SYNOPSIS
DESCRIPTION
RETURN VALUE
ERRORS
VERSIONS
CONFORMING TO
NOTES
EXAMPLE
SEE ALSO
COLOPHON





Support us on Content Nation
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2020 Sascha Nitsch Unternehmensberatung GmbH
Valid XHTML1.1 : Valid CSS : buttonmaker
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 9.6 ms