Re: Bug: font caching on OS X w/ networked home folders

[Patrick McCarty]

On 2010-02-04, Jacob Rundall wrote:
> Thanks.  I searched both the client and the server to see if any
> font cache files were being created elsewhere and this doesn't seem
> to be the case.  I do have the following the client's system.log
> file however:
> 
> Feb  2 11:26:29 camil15 kernel[0]: encodings.dir/rsrc: file access
> by '/rsrc' was deprecated in 10.4
> Feb  2 11:26:29 camil15 kernel[0]: fonts.dir/rsrc: file access by
> '/rsrc' was deprecated in 10.4
> Feb  2 11:26:29 camil15 kernel[0]: fonts.list/rsrc: file access by
> '/rsrc' was deprecated in 10.4
> Feb  2 11:26:29 camil15 kernel[0]: fonts.scale/rsrc: file access by
> '/rsrc' was deprecated in 10.4
> Feb  2 11:27:02 camil15 kernel[0]: Helvetica LT MM/rsrc: file access
> by '/rsrc' was deprecated in 10.4
> Feb  2 11:27:02 camil15 kernel[0]: Keyboard.dfont/rsrc: file access
> by '/rsrc' was deprecated in 10.4
> Feb  2 11:27:02 camil15 kernel[0]: LastResort.dfont/rsrc: file
> access by '/rsrc' was deprecated in 10.4
> Feb  2 11:27:02 camil15 kernel[0]: Times LT MM/rsrc: file access by
> '/rsrc' was deprecated in 10.4
> Feb  2 11:27:02 camil15 kernel[0]: encodings.dir/rsrc: file access
> by '/rsrc' was deprecated in 10.4
> Feb  2 11:27:02 camil15 kernel[0]: fonts.dir/rsrc: file access by
> '/rsrc' was deprecated in 10.4
> Feb  2 11:27:02 camil15 kernel[0]: fonts.list/rsrc: file access by
> '/rsrc' was deprecated in 10.4
> Feb  2 11:27:02 camil15 kernel[0]: fonts.scale/rsrc: file access by
> '/rsrc' was deprecated in 10.4
> 
>  I suspect this does in fact indicate that fontconfig is failing,
>  right?

Sorry, I forgot to follow up on this.

A quick Google search leads me to believe that these warnings are
caused by Freetype (a dependency of LilyPond) using a deprecated
method of accessing resource forks (whatever those are) on Mac OS X.

See http://trac.macports.org/ticket/18859.

While it sounds like they are just harmless warnings, I guess it
wouldn't hurt to try applying the patch MacPorts is using.

Are there any other warnings or errors showing up in the console log
on client or server that look suspicious?

Thanks,
Patrick