You can save disk space and reduce RAM usage on
your system by configuring VUE to be a font client, which accesses fonts
from a network font server. You can configure your system as a font
client (or a font server) during the first-time startup of your system.
The following section describes some restrictions to setting up a font
client.
Being a font client lets the VUE environment operate without having the
X11 font filesets on disk. This saves 8 MBs or more of disk space, and
much more on systems with Asian fonts. X11 fonts are accessed over the
network from a font server.
Some Conditions When Using Font Servers. Only systems with local graphics displays running VUE should be font clients.
Being a network font client makes your VUE interface somewhat dependent on the network and the font server host.
For this reason, you might want to use font clients only on reliable systems that are connected by reliable networks.
See the mk_fnt_clnt(1M) man page for further details.
Restrictions on Font Clients. Configuring a system to be a font client is a trade-off for systems that have limited disk space or reduced amounts of RAM.
NFS diskless servers or clients should never be configured as font clients. Before configuring an existing font client to be a diskless server, you should restore the X11 font filesets as described under “To stop being a font client”.
In general, any server system providing X11 or VUE resources to other clients (such as a system serving X terminals or an MPower server) should not be a font client.
If your system uses something other than VUE 3.0 for its X11 interface, you should not make the system a font client.
To set up a font server |
 |
Before configuring a system to be a client of a font server, you must
first configure the server.
If you completed the first-time startup and did not choose to configure
the system as font server at that time, you can still do so.
You can configure a font server (or client) on 10.0 systems by running
the interactive script:
or non-interactively by running the command:
See the mk_fnt_srvr(1M) man page for further details.
If your font server system is running HP-UX Release 9.x instead of 10.0,
you will need to manually start the fs(1) daemon and ensure that it is
restarted after every reboot.
To set up a font client |
|
If you completed the first-time startup and did not choose to configure
the system as a font client at that time, you can still do so.
You can configure a font client (or server) on 10.0 systems by running
the interactive script:
or non-interactively by running the command:
You will need the name, and possibly the IP address, of a host that is
currently running the font server daemon. A number of font filesets
will be removed from your system.
See the mk_fnt_clnt(1M) man page for further details.
To stop being a font client |
|
If you decide to have a system cease to be a network font client and
return to accessing fonts from your filesystem, use the following steps:
Reload the desired X11 font filesets using swinstall.
Remove the line from the /etc/rc.config.d/vuerc file that begins with:
Exit any active VUE sessions and restart the X server.
To change the font server |
|
You can change the name of the font server host used by your font client to another server by executing the interactive script:
or non-interactively by running the command:
See the mk_fnt_clnt(1M) man page for further details.
Printable version
