Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rainer Weikusat Newsgroups: comp.os.linux.development.apps Subject: Re: mkdir() and thread safety() Date: Fri, 01 Apr 2011 21:23:50 +0100 Lines: 9 Message-ID: <877hbdk9ex.fsf@sapphire.mobileactivedefense.com> References: <9d56213c-a054-428e-866c-559da29fbbc3@o21g2000prh.googlegroups.com> <2d58ece6-bb9c-42e0-a990-fc13b92723ec@a21g2000prj.googlegroups.com> <87oc4vtn8o.fsf@sapphire.mobileactivedefense.com> <87tyejtx4u.fsf@sapphire.mobileactivedefense.com> <35d2db97-6ab2-42b1-a83a-c4764f3c3869@w7g2000pre.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net DYkyij0Xa9d67Hsqhw9PEQESSZn4BJlW2Nycefbp3aP04vOZk= Cancel-Lock: sha1:i5Tt0N2iqnnaijcRJjGs8y3g8ro= sha1:BSW0NwWZItOYdSIZ3PMMjCZWtGA= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.development.apps:65 David Schwartz writes: > The operation starts when the application calls 'mkdir'. The standard > only requires the operation to fail with EEXIST if the directory > exists before the operation starts. An additional error in here I'd like to point out: Code which runs after mkdir was called cannot check if such a file existed before mkdir was called. It would need to be able to travel back in time for this.