There seems another situation that corrupts the cache: https://bugzilla.redhat.com/show_bug.cgi?id=921706 Even re-scanning directories seems not help in some cases. strange. I have no idea at this moment to get a fix of this issue. I'll look into it more though. On Wed, Oct 2, 2013 at 4:18 PM, Akira TAGOH <akira@xxxxxxxxx> wrote: > On Wed, Oct 2, 2013 at 4:07 AM, Akira TAGOH <akira@xxxxxxxxx> wrote: >> Right. that said I suppose it may be useful only when it is the >> singleton process, in fact this issue happened with sleep one second. >> at least waiting for one sec just before exiting didn't help. it might >> be better moving between reading the directory and writing the cache >> perhaps. so it might catches up updates on reading caches. let me try >> that later. > > That also works but we need to support the parallel updates on > fc-cache by threading then. otherwise it's quite stressful to wait > for. but it may takes more time if the directory structure where is > updating is too deep, because there are no way to know how many sub > directories it contains until a cache is updated. so just updating > twice seems realistic at this moment. this may be a todo task for > future improvement. > > -- > Akira TAGOH -- Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
