Re: os.stat access and modify time same on WinXP
From: Peter Hansen (peter_at_engcorp.com)
Date: 03/23/05
- Next message: Peter Hansen: "Re: Windows, Python and low level networking"
- Previous message: Jaime Wyant: "Re: Windows, Python and low level networking"
- In reply to: rbt: "os.stat access and modify time same on WinXP"
- Next in thread: rbt: "Re: os.stat access and modify time same on WinXP"
- Reply: rbt: "Re: os.stat access and modify time same on WinXP"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 23 Mar 2005 12:02:02 -0500
rbt wrote:
> I'm using the standard NTFS file system. The only time the access time
> is updated is when the file is modified or saved (with no changes).
> What's up with that? Shouldn't a read/view update the access time?
Quoting:
'''
The Last Access Time on disk is not always current because NTFS looks
for a one-hour interval before forcing the Last Access Time updates to
disk. NTFS also delays writing the Last Access Time to disk when users
or programs perform read-only operations on a file or folder, such as
listing the folder's contents or reading (but not changing) a file in
the folder. If the Last Access Time is kept current on disk for read
operations, all read operations become write operations, which impacts
NTFS performance.
Note
* File-based queries of Last Access Time are accurate even if all
on-disk values are not current. NTFS returns the correct value on
queries because the accurate value is stored in memory.
'''
Does that help?
(Just went through this myself the other day.)
-Peter
- Next message: Peter Hansen: "Re: Windows, Python and low level networking"
- Previous message: Jaime Wyant: "Re: Windows, Python and low level networking"
- In reply to: rbt: "os.stat access and modify time same on WinXP"
- Next in thread: rbt: "Re: os.stat access and modify time same on WinXP"
- Reply: rbt: "Re: os.stat access and modify time same on WinXP"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
