Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-Id: <3.0.5.32.20030101214858.007f17f0@h00207811519c.ne.client2.attbi.com> X-Sender: pierre@h00207811519c.ne.client2.attbi.com Date: Wed, 01 Jan 2003 21:48:58 -0500 To: cygwin@cygwin.com, cygwin@cygwin.com From: "Pierre A. Humblet" Subject: Re: Heads up: *possible* bug in cygwin In-Reply-To: <20030102000112.GB24893@redhat.com> References: <20030101211342.GA35586973@HPN5170X> <20030101100510.5b5b7f3f.steven.obrien2@ntlworld.com> <20030101170613.GA19419@redhat.com> <20030101171952.GA83996745@HPN5170X> <20030101173445.GA1354@redhat.com> <20030101194854.GA19827@redhat.com> <20030101211342.GA35586973@HPN5170X> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 07:01 PM 1/1/2003 -0500, Christopher Faylor wrote: >Oops. You're right. So, the only potential problem is that the getpw >routines aren't thread safe. There is a window during the passwd info >resides in a static structure. You are right, the routines are not thread safe. However everything should be fine unless passwd or group are changed while a program is running. That's probably not the case here. Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/