Re: Cached file '...' has a future timestamp

J=F6rg Sommer <[email protected]> writes:

> I get tones of these messages, everytime the purge process runs. Why they
> are triggered?
>
> # grep -Fc 'has a future timestamp' /var/log/daemon.log
> 38665
> # grep -F 'has a future timestamp' /var/log/daemon.log S -n '1p; $p'
> Jan 11 07:46:14 alea wwwoffled[6975]: Cached file 'http/www.weibeldruck.c=
h/UpXZuf-PUImJmdwQqpOVkZA' has a future timestamp; changing timestamp.
> Jan 11 09:23:26 alea wwwoffled[6975]: Cached file 'ftp/ftp.de.debian.org/=
UJyiy5o+zKfj1LVtkioKj+g' has a future timestamp; changing timestamp.

I don't know why this happens.

I have been through the code and in all the places that I set the
timestamp on a file it is for one of two reasons:

1) To set the timestamp to now

This happens a few times, but there isn't a consistent reason.
Normally it is to indicate that a change has been made to a directory.

2) To set the timestamp back to the value it had before.

For example when compressing a file during a purge of the cache the
file timestamp is set to the original time of the file, not the time
it was compressed.


I can't see any case that a file time in the future would be
deliberately created by WWWOFFLE.

--=20
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop                             amb-Uxr6IM1mbv2TY6FTCsQk+9Bc4/[email protected]
                                      http://www.gedanken.demon.co.uk/

WWWOFFLE users page:
        http://www.gedanken.demon.co.uk/wwwoffle/version-2.9/user.html