Known issues with filemtime () on Windows - files to be affected arbitrarily?
Is there a known issue causing the cache file files to change temporarily in Windows XP SP 3, which will be randomly updated but without any changes?
Is there any service in standard Windows XP - Backup, Sync, Versioning, Virus scanner - known regarding files? They all have an extension .txt
.
If not, forget about it. Then I get something wrong in my caching routines and I will debug my way.
Background:
I am creating a simple caching wrapper around a slow website on a windows server.
I am comparing the timestamp filemtime()
with some columns in the database to determine if the cached file is outdated.
I am having trouble using this method because the modification times of the cache files seem to be updated between operations and I am not doing anything. This leads to the display of obsolete files.
I am the only user on the machine. Operating System - Windows XP, XAMPP Apache 2 Web Server with PHP 5.2
a source to share
You can set up logging * on your computer to see what changes your files. From your description, I do this a lot, so you can find ProcessMonitor ( German ) to be the best monitoring solution.
*
I think you can set up the logging with the built-in tools, just not sure more
a source to share
The only mtime problem I can think of is the dreaded DST error . It doesn't look like what you are getting.
Of course, there are other Windows tools that can modify the file behind your back, but usually it's a custom level like WMP screwing with ID3 tags, or quirky AV ... not something I would expect to touch your cache files ...
(Maybe you could try to compare the equality of mtimes rather than more or less using just the cache if there is an exact match? This at least means that if some antisocial expiring channel touches the files, I just slow you down a bit. instead of forcing you to serve outdated files.FWIW is what Python does with the bytecode cache.)
a source to share