Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Mon, 11 Nov 2002 18:01:40 +0100 From: Corinna Vinschen To: cygwin-developers AT cygwin DOT com Subject: Re: ntsec patch #4: passwd and group Message-ID: <20021111180140.Z10395@cygbert.vinschen.de> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <3DCBD52C DOT A1F794FD AT ieee DOT org> <20021108171918 DOT P21920 AT cygbert DOT vinschen DOT de> <3DCBEFF5 DOT 850B999E AT ieee DOT org> <20021111145612 DOT T10395 AT cygbert DOT vinschen DOT de> <3DCFC6BB DOT 570DF472 AT ieee DOT org> <20021111174720 DOT X10395 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021111174720.X10395@cygbert.vinschen.de> User-Agent: Mutt/1.3.22.1i On Mon, Nov 11, 2002 at 05:47:20PM +0100, Corinna Vinschen wrote: > I don't think it makes sense to use a sophisticated mutex thingy for > reading passwd/group info. See below. Oops, I forgot the "below". Actually, the problem might be a problem only in multi-threaded apps. Our server processes typically aren't. And if the application is multi-threaded, it must additionally read passwd/group from multiple threads. That's pretty much unlikely. So a simple mutex should be enough, IMHO. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc.