Date: Thu, 5 Oct 2000 16:22:56 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: "Jacques A. Vidrine" <n@nectar.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: _THREAD_SAFE in libc Message-ID: <20001005162255.T27736@fw.wintelcom.net> In-Reply-To: <20001005181751.A68499@hamlet.nectar.com>; from n@nectar.com on Thu, Oct 05, 2000 at 06:17:51PM -0500 References: <20001005181751.A68499@hamlet.nectar.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Jacques A. Vidrine <n@nectar.com> [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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001005162255.T27736>