Re: problem with updates to file last modified time
Re: problem with updates to file last modified time
- Subject: Re: problem with updates to file last modified time
- From: Alan Snyder <email@hidden>
- Date: Sat, 03 Dec 2016 07:57:22 -0800
Hi Tom,
Thanks for that information. Sounds like my test program should retry as needed when modifying a file to be sure that it actually changes the visible attribute.
Alan
> On Dec 3, 2016, at 3:05 AM, Thomas Tempelmann <email@hidden> wrote:
>
> Hi Alan,
> what makes you think that you get such a high resolution with the file dates? Most file systems only have a one second resolution (some even have less), meaning you have to wait for a second to actually see the value on disk change. So, even if the OS would use a higher resolution in its APIs, it would only be held in memory, not on disk. I'd question that bevavior, though - the APIs should not suggest a higher res than what the actual on-disk structure can support. Regardless - if some rare event would clear the in-memory cache, you'd get back the on-disk value with the lower resolution, and that could be what you're seeing. Unless I totally misunderstand what you're doing.
>
> Thomas
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden