Re: open() fails to update st_mtime when used with O_TRUNC and 0 byte files
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com and i've been informed that a test already exists that should match the behavior i'm describing: POSIX.os/files/open 19 i'm testing 10.4.x and not 10.5 (which is the version that was certified), so perhaps 10.5 has already been fixed ? -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... On Jul 11, 2007, at 4:00 PM, Mike Frysinger wrote: On 7/10/07, Mike Frysinger <vapier.adi@gmail.com> wrote: On 7/9/07, Terry Lambert <tlambert@apple.com> wrote:
Maybe you could get them to add it as a test case for the test suite,
if they (specifically, The Austin Group, actually) agreed with your
interpretation of the standard. so the answer to my query on the Austin Group mailing list is that the
way ive interpreted the standard is the correct interpretation ... POSIX conforming systems must: - update st_mtime when opened with O_TRUNC regardless of the size of the file before hand - make sure st_ctime/st_mtime are properly available at the next relevant point in time (like when calling stat() or fstat()) i'll look into getting a test added to the POSIX testsuite Sorry, can't make forward looking statements; you'd need to talk to your DTS representative. This email sent to site_archiver@lists.apple.com
participants (1)
-
Terry Lambert