what’s with the 11/1979 date of the text files in /results?
that is causing immense headaches when trying to do some internal archiving and windowing of those files - in an effort to intelligently export them into an area that can be consumed by other processes.
can you simply timestamp them with the time they are actually created?
7081534 4 -rw-rw-rw- 1 apache apache 4080 Nov 30 1979 /var/www/html/results/14/03/01/0X/P8/1_pagespeed.txt
7081537 4 -rw-rw-rw- 1 apache apache 302 Nov 30 1979 /var/www/html/results/14/03/01/0X/P8/1_status.txt
7081536 4 -rw-rw-rw- 1 apache apache 3638 Nov 30 1979 /var/www/html/results/14/03/01/0X/P8/1_report.txt
7081490 8 -rw-rw-rw- 1 apache apache 4521 Nov 30 1979 /var/www/html/results/14/03/01/0X/P8/1_IEWPG.txt
7081533 160 -rw-rw-rw- 1 apache apache 160471 Nov 30 1979 /var/www/html/results/14/03/01/0X/P8/1_IEWTR.txt
I’ve never seen a timestamp issue like that. Are the clocks on both your server and the test agents reasonably close to current?
Yes - i just checked the server and 3 machines that are running agents. All in EC2, and all set to Greenwich Time (3 Windows machines) and UTC (linux).
All have current time and within 1 second of each other.
I can tweak the server to touch the files as it receives them instead of just moving them from the upload folder. The created time won’t change but the last-modified should show up as current.
That would be helpful - right now i run a cron job that touches files with modify dates > 20 years or something like that.
interestingly, looking into the details of generic file time info in linux, it seems there are only 2 times available for a file - when the contents were last modified and when the status was last modified - but not the create date. i’m no expert, but that’s what i recall when trying to figure out what was going on here.