Re: Wishlist: credential file update/access collision avoidance?
Nico Williams <[email protected]>
| Newsgroups | gmane.comp.encryption.kerberos.heimdal.general |
|---|---|
| Message-ID | <CAK3OfOj-ZoXi0V5UQ822Qk+hJS=PSNkro_ewdNvVm8RsW_0zoA@mail.gmail.com> |
On Mon, Oct 3, 2011 at 3:20 PM, Jeffrey Hutzelman <[email protected]> wrote: >> What we mean here (what I take to have been meant) by POSIX semantics >> here is not necessarily strict adherence to POSIX, but things like >> "unlink() of open files is allowed" and "rename() is atomic and >> unlink()s whatever file might have existed with the target name" -- >> that sort of thing. > > That was not at all clear to me from context. > > Certainly I think it is reasonable to assume that a filesystem used > for /tmp will have those particular properties. This is getting rather OT, but, when people refer to POSIX filesystem semantics I almost always understand it to refer to such rules (as well as to others such as write visibility rules, and even the horrid first-close-drops-locks rule). The sorts of semantics that Unix programmers typically take for granted. Nico --