Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.development.apps > #59
| From | Rainer Weikusat <rweikusat@mssgmbh.com> |
|---|---|
| Newsgroups | comp.os.linux.development.apps |
| Subject | Re: mkdir() and thread safety() |
| Date | 2011-03-31 11:17 +0100 |
| Message-ID | <87pqp7tx0a.fsf@sapphire.mobileactivedefense.com> (permalink) |
| References | <9d56213c-a054-428e-866c-559da29fbbc3@o21g2000prh.googlegroups.com> <2d58ece6-bb9c-42e0-a990-fc13b92723ec@a21g2000prj.googlegroups.com> <87oc4vtn8o.fsf@sapphire.mobileactivedefense.com> <d18b0392-2e9d-49e5-911b-0b0a07c3f082@i35g2000prd.googlegroups.com> <87lizwjln1.fsf@araminta.anjou.terraraq.org.uk> |
Richard Kettlewell <rjk@greenend.org.uk> writes: > David Schwartz <davids@webmaster.com> writes: >> Rainer Weikusat <rweiku...@mssgmbh.com> wrote: >>> Also, the UNIX(*) standard demands that mkdir is supposed to fail >>> with EEXIST when the named file already existed. This is not possible >>> when mkdir is not an atomic operation. >> >> Yes, it is. The algorithm I specified will always fail if the named >> file already existed before the operation started. There is no >> requirement for atomicity. You can't just make up requirements because >> they seem reasonable to you. > > I'd go further than that: even when there is a standardized requirement > for atomicity (or any other property), you may still need to check what > the implementation does. NFS's failure to properly support O_EXCL is > notorious. You actually need to do so because Kennedy was shot, clearly proving that all kinds of things nobody expects CAN and DO happen ...
Back to comp.os.linux.development.apps | Previous | Next — Previous in thread | Next in thread | Find similar
Re: mkdir() and thread safety() David Schwartz <davids@webmaster.com> - 2011-03-30 14:53 -0700
Re: mkdir() and thread safety() Richard Kettlewell <rjk@greenend.org.uk> - 2011-03-30 23:20 +0100
Re: mkdir() and thread safety() Rainer Weikusat <rweikusat@mssgmbh.com> - 2011-03-31 11:17 +0100
Re: mkdir() and thread safety() Rainer Weikusat <rweikusat@mssgmbh.com> - 2011-03-31 11:14 +0100
Re: mkdir() and thread safety() George Neuner <gneuner2@comcast.net> - 2011-03-31 19:13 -0400
Re: mkdir() and thread safety() Rainer Weikusat <rweikusat@mssgmbh.com> - 2011-04-01 16:52 +0100
Re: mkdir() and thread safety() George Neuner <gneuner2@comcast.net> - 2011-04-03 13:59 -0400
Re: mkdir() and thread safety() Rainer Weikusat <rweikusat@mssgmbh.com> - 2011-04-08 23:59 +0100
Re: mkdir() and thread safety() David Schwartz <davids@webmaster.com> - 2011-04-01 12:22 -0700
Re: mkdir() and thread safety() Rainer Weikusat <rweikusat@mssgmbh.com> - 2011-04-01 21:03 +0100
Re: mkdir() and thread safety() David Schwartz <davids@webmaster.com> - 2011-04-01 14:27 -0700
Re: mkdir() and thread safety() Rainer Weikusat <rweikusat@mssgmbh.com> - 2011-04-01 21:23 +0100
Re: mkdir() and thread safety() David Schwartz <davids@webmaster.com> - 2011-04-01 14:28 -0700
csiph-web