Thank you for testing. it may be time to revert the changes in fontconfig. will work on that. On Wed, Mar 30, 2016 at 5:19 AM, Raimund Steger <rs@xxxxxxxx> wrote: > On Tue, 15 Mar 2016 01:58:53 +0100 > Raimund Steger <rs@xxxxxxxx> wrote: > >> On Sun, 13 Mar 2016 13:40:41 -0700 >> Behdad Esfahbod <behdad@xxxxxxxxxx> wrote: >> > [...] >> > There are four usecases we need to consider: >> > >> > - Normal Linux / other Unix-like. We can assume high-precision >> > timestamps are available and take care of stuff, >> > >> > - Linux / Unix-like system with network file system. Any issues there >> > with your proposed patch? >> >> NFSv3 spec has nanoseconds, but I think server support is optional. I'll do some research what kind of support currently is out there. The implementations I'm using here seem to support it. Even if not, there might be little choice, as the stat penalty is most severe with NFS and 2.11 behavior is more acceptable IMHO. > > I've now tested the server and client sides of Solaris 11.2, FreeBSD 10.1, and Debian 7.9. From what I can see they all support highres timestamps with NFSv3. > > > > -- > Worringer Str 31 Duesseldorf 40211 DE home: rs@xxxxxxxx > +49-179-2981632 icq 16845346 work: rs@xxxxxxxxxxxxxxx > _______________________________________________ > Fontconfig mailing list > Fontconfig@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/fontconfig -- Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/fontconfig
