Keith Packard wrote: > Looks like it's an NFS timestamping issue. Fontconfig checks to make > sure the cache file is no older than the directory before using it, and > if your clocks are out of sync, it may well be. It might be best if > fontconfig wrote the timestamp to the file instead of of using the file > system time. > > Meanwhile, you might make sure the NFS server times are close to your > local system time.
My systems are both NTPed and seem to be quite close to each other (under 1 second). I changed the NFS client to sync against it's server's NTP server, just to make sure. OTOH, this system _was_ installed with a clock that was originally a couple hours out of wack. Then I fixed the clock. Could a fontconfig cache that seemed to be several hours in the future have caused it? -- see shy jo
signature.asc
Description: Digital signature
