copying pthread_mutex_t, pthread_cond_t - comp.unix.programmer

Message from discussion copying pthread_mutex_t, pthread_cond_t
Path: g2news2.google.com!postnews.google.com!b9g2000yqm.googlegroups.com!not-for-mail
From: James Kanze <james.ka...@gmail.com>
Newsgroups: comp.unix.programmer
Subject: copying pthread_mutex_t, pthread_cond_t
Date: Sat, 4 Jul 2009 02:50:03 -0700 (PDT)
Organization: http://groups.google.com
Lines: 15
Message-ID: <11b4bf56-2145-4bce-bfec-116e4d92957a@b9g2000yqm.googlegroups.com>
NNTP-Posting-Host: 79.95.48.241
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1246701004 10041 127.0.0.1 (4 Jul 2009 09:50:04 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 4 Jul 2009 09:50:04 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: b9g2000yqm.googlegroups.com; posting-host=79.95.48.241; 
	posting-account=1W_PtwoAAAA1QoMcl2Z5P6j-DNc8HR3W
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.11) 
	Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11,gzip(gfe),gzip(gfe)

Not sure this is the best group: my question concerns the actual
Posix standard, and what it says.

Basically, is it legal to copy a pthread_mutex_t or a
pthread_cond_t, and use the copy?  If not (which is the only
answer which makes sense to me), where does the Posix
specification say this?  If so, what does it mean: what happens,
for example, if a copy a mutex which is held by a thread, wait
on the copy, and the holding thread frees the original?

--
James Kanze (GABI Software)             email:james.ka...@gmail.com
Conseils en informatique orient=E9e objet/
                   Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34