The following issue has been CLOSED
==
https://www.opencsw.org/mantis/view.php?id=1519
==
Reported By:asmoore
Assigned To:amaier
==
Project:fontconfig
Issue ID: 1519
Category: packaging
Reproducibility:always
Severity: feature
Priority: normal
Status: closed
Resolution: open
Fixed in Version:
==
Date Submitted: 2006-03-05 09:22 CET
Last Modified: 2013-11-17 09:52 CET
==
Summary:fc-cache running in non-global zone
Description:
On Solaris 10 in a non-global zone; fc-cache produces error after error.
==
--
(0003224) asmoore (reporter) - 2006-03-05 10:04
https://www.opencsw.org/mantis/view.php?id=1519#c3224
--
Actually, your question is my question and the problem.
One of the ways to setup a non-globabl zone, and this is probably the most
typical, is to mount /usr from the global zone in the non-global zones with
lofs. The mount is -ro in the non-global zone.
I installed a package in a non-global zone and pkg-get installed fontconfig
as a dependency. Therefore, I suspect that fc-cache was started from
postinstall. After running at very heavy cpu utilization and spitting out
error after error, I finally got the process to die.
You can use /usr/bin/zonename, if it exists, to determine the zonename. I
believe this is correct, but you may want to confirm, zonename returns
\'global\' when run from the global zone. If the zonename binary exists
and does not return \'global\', you may want to send a message that
fc-cache was not run and, if needed, can be run with the init script.
