On Wed, Jan 13, 2016 at 12:29 AM, Keith Packard <keithp@xxxxxxxxxx> wrote: > Here's another alternative -- cache creation could be the responsibility > of fc-cache, but perhaps applications could validate the cache by > checking directory timestamps and loading directories which were out of > date manually (as they do today) but *not* write out that information > back to the disk which would avoid the race conditions present in the > current environment. fc-cache could then use some kind of per-directory > locking to avoid races in generating the information there, which should > make the directory timestamps reliable enough to not need applications > to scan every directory manually at startup time. But it will takes a lot of times at startup every time when bringing up applications if the cache is outdated. it looks like worse than now. and the issue I faced is came from the parallel running of fc-cache and traversing deep directories. I don't think it does help for them. -- Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
