From: Bryan Holloway <bryan@...>
Date: Wed, 30 Oct 2002 11:02:33 -0600
After the time-switchover this weekend, we have files with the wrong
modification dates. They're off by, as you can imagine, an hour. Bug
in afpd? I saw an old reference to this problem last year, but didn't
know if it was still an issue.
There was a discussion of this on 9 April 2001. The consensus was that
this was a client bug. The filesystem stores UTC times (Unix encoded),
and netatalk ships the UTC values unmodified over the wire, which is the
format required by the AFP spec. But there was no conclusion as to
which client versions were buggy, though it happens for me with vanilla
I've written code to change the mod-date in the corresponding files'
resource forks, but I'm afraid to run it on the whole server. Where
does afpd get the mod-date if there is no resource fork?
AFAIK, the AFP mod time is taken directly from the Unix stat mod time.
So this probably won't help, and may break things.
-- Bob Rogers