Re: open() fails to update st_mtime when used with O_TRUNC and 0 byte files
Re: open() fails to update st_mtime when used with O_TRUNC and 0 byte files
- Subject: Re: open() fails to update st_mtime when used with O_TRUNC and 0 byte files
- From: "Mike Frysinger" <email@hidden>
- Date: Wed, 11 Jul 2007 23:45:58 -0500
On 7/11/07, Terry Lambert <email@hidden> wrote:
On Jul 11, 2007, at 4:00 PM, Mike Frysinger wrote:
> On 7/10/07, Mike Frysinger <email@hidden> wrote:
>> On 7/9/07, Terry Lambert <email@hidden> 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
>
> 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 ?
Sorry, can't make forward looking statements; you'd need to talk to
your DTS representative.
i dont even know what a "DTS representative" ... my guess is you're
punting me to the marketing team or something ? how is it a forward
looking statement if 10.5 has already been certified ?
-mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden