From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22995 invoked by alias); 8 Sep 2004 16:38:19 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 22977 invoked from network); 8 Sep 2004 16:38:18 -0000 Received: from unknown (HELO Cantor.suse.de) (195.135.220.2) by sourceware.org with SMTP; 8 Sep 2004 16:38:18 -0000 Received: from hermes.suse.de (hermes-ext.suse.de [195.135.221.8]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by Cantor.suse.de (Postfix) with ESMTP id 483EEBAD856 for ; Wed, 8 Sep 2004 18:38:18 +0200 (CEST) Date: Wed, 08 Sep 2004 16:38:00 -0000 From: Thorsten Kukuk To: libc-hacker@sources.redhat.com Subject: Re: Questions about __thread for NSS modules Message-ID: <20040908163818.GA15431@suse.de> References: <20040826095808.GA6880@suse.de> <200408261020.i7QAKVE9018030@magilla.sf.frob.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408261020.i7QAKVE9018030@magilla.sf.frob.com> Organization: SuSE Linux AG, Nuernberg, Germany User-Agent: Mutt/1.5.6i X-SW-Source: 2004-09/txt/msg00029.txt.bz2 On Thu, Aug 26, Roland McGrath wrote: > > My question is: is this possible at all in NSS modules like libnss_nis.so? > > Sure. Ok, I managed now to build a libnss_nis.so.2 module, which uses thread local storage instead of static variables and locking. Now my next problem: SuSE and RH have the libc/libpthread with TLS and NPTL support in /lib/tls and a version without in /lib. But the path to the libnss_* modules is hardcoded to /lib/libnss_*. So I cannot copy the libnss_nis module with TLS support into /lib/tls/. Any ideas how to solve this? Thanks, Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Maxfeldstr. 5 D-90409 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B