X-Spam-Check-By: sourceware.org Date: Fri, 27 Jan 2006 19:26:55 +0100 From: Alex Riesen To: Eric Blake Cc: cygwin@cygwin.com Subject: Re: cygwin-1.5.19-2: mkdir returns inconsistent errno Message-ID: <20060127182655.GA6169@steel.home> Reply-To: Alex Riesen References: <012620061525.1038.43D8EA05000B44680000040E22007358340A050E040D0C079D0A@comcast.net> <81b0412b0601260821p2a0525dane12307a43e6897f1@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <81b0412b0601260821p2a0525dane12307a43e6897f1@mail.gmail.com> User-Agent: Mutt/1.5.6i Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Alex Riesen, Thu, Jan 26, 2006 17:21:21 +0100: > > > > > This is highly unexpected, does not match linux behaviour > > > > > (it returns EEXIST), and actually breaks git (git clone, > > > > > creation of pathnames, to be precise). > > > > > > > > Then git has a bug. Report it there. To be portable > > > > when making pathnames, you must first check > > > > for directory existance rather than relying on an > > > > errno of EEXIST to tell you the directory exists. > > > > > > How do you do it race-free? > > > > chdir(). If chdir() succeeded, then the directory existed, > > regardless of the errno that mkdir() reported. > > Take a look at gnulib's mkdir-p.c module: > > http://cvs.savannah.gnu.org/viewcvs/gnulib/lib/mkdir-p.c?rev=1.5&root=gnulib&view=auto > > Very interesting! Thank you for this and the other references. > I'm given hope! :) This was a bit prematurely. There is a big problem with this aproach: it changes current directory of the process. So you can't really use it in multithreaded or signalled environment. So chdir is not a real solution. Is it really that hard to workaround the problem in cygwin? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/