From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Luka Marinko <luka.marinko@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: question on pthreads
Date: Mon, 21 Aug 2006 06:45:31 -0400 [thread overview]
Message-ID: <44E98ECB.3040603@cfl.rr.com> (raw)
In-Reply-To: <1156112486.10565.64.camel@mindpipe>
Lee Revell wrote:
> On Sun, 2006-08-20 at 21:32 +0000, Luka Marinko wrote:
>> You can find nice manual here, and overview
>> http://www.gnu.org/software/libc/manual/html_mono/libc.html
>>
>
> Unfortunately the NPTL documentation is FAR from complete - there are no
> man pages at all, and some featured are completely undocumented. For
> example process-shared mutexes are supported, but the only way you'd
> know is to look at the source. The only docs I could find on how to use
> them were old Solaris man pages.
>
> Lee
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
glibc 2.4.31 has a man page for it.
PTHREAD_MUTEXATTR_GETPSHARED(P) POSIX
Programmer's Manual PTHREAD_MUTEXATTR_GETPSHARED(P)
NAME
pthread_mutexattr_getpshared, pthread_mutexattr_setpshared - get and set
the process-shared attribute
SYNOPSIS
#include <pthread.h>
int pthread_mutexattr_getpshared(const pthread_mutexattr_t *
restrict attr, int *restrict pshared);
int pthread_mutexattr_setpshared(pthread_mutexattr_t *attr,
int pshared);
Mark
next prev parent reply other threads:[~2006-08-21 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 17:46 question on pthreads Irfan Habib
2006-08-20 19:37 ` Nix
2006-08-20 21:32 ` Luka Marinko
2006-08-20 22:21 ` Lee Revell
2006-08-21 10:45 ` Mark Hounschell [this message]
2006-08-29 0:21 ` Nix
2006-08-29 11:51 ` Mark Hounschell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44E98ECB.3040603@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.marinko@gmail.com \
--cc=rlrevell@joe-job.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox