<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Make fontconfig scanning faster"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64766#c42">Comment # 42</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Make fontconfig scanning faster"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64766">bug 64766</a>
from <span class="vcard"><a class="email" href="mailto:akira@tagoh.org" title="Akira TAGOH <akira@tagoh.org>"> <span class="fn">Akira TAGOH</span></a>
</span></b>
<pre>(In reply to Timo Teräs from <a href="show_bug.cgi?id=64766#c40">comment #40</a>)
<span class="quote">> > - Remove the 2s wait if file system is not FAT. This one is not really
> > important, but nice to have.
>
> This is not done yet. And I'd really like this to go in before the next
> release. Would it be possible to push this out? I see recent commit now even
> taking into account the nanosecond field of mtime... this two second delay
> is pretty much harmful. If FAT is of concern still, it should have
> additional code to 'touch' the file until the stat() returned time is
> changed, or something similar.</span >
Hmm, it is easier to have a wait in case the targeted FS is FAT. current code
has enough functionality to do that. but the problem is that wait itself seems
not meaningless so that fc-cache isn't a singleton process and easy to conflict
with the multiple processes on current code base.
Though it might be better than do nothing.
If there are any better idea, the suggestions are welcome.
I may go ahead with checking fs type for a workaround to see if fc-cache should
wait for 2s or not otherwise.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>