From owner-freebsd-hackers Thu Oct 5 16:23: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2118937B503 for ; Thu, 5 Oct 2000 16:23:01 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e95NMu910844; Thu, 5 Oct 2000 16:22:56 -0700 (PDT) Date: Thu, 5 Oct 2000 16:22:56 -0700 From: Alfred Perlstein To: "Jacques A. Vidrine" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: _THREAD_SAFE in libc Message-ID: <20001005162255.T27736@fw.wintelcom.net> References: <20001005181751.A68499@hamlet.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001005181751.A68499@hamlet.nectar.com>; from n@nectar.com on Thu, Oct 05, 2000 at 06:17:51PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jacques A. Vidrine [001005 16:18] wrote: > Is it ok to use pthread_rwlock* and other such primitives in code in > src/lib/libc (when _THREAD_SAFE is defined, of course)? > > I ask because I don't see any other code doing this. Perhaps there is a > private interface to use? Perhaps I'm barking up the wrong tree? > > Context: I want to make nsdispatch thread safe (inasmuch as possible-- > e.g. I'm not tackling the resolver), so I need to protect its data > structures. It sure looks like it. cd /usr/src/lib/libc/ ; grep pthread */* -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message