
HP OpenView NetMetrix/UX Release Notes version 6.0
October 1, 1998
Known Problems and Work-Arounds
18 October 1, 1998
Description Fonts used for display are too large
Details If you run NetMetrix applications while the X display is set to another,
the resulting windows may use larger than expected fonts. The problem
occurs if NetMetrix is not installed on the X display host.
Work-Around To ensure that proper fonts are used, copy the X resources file /usr/lib/
X11/app-defaults/Netm from the system that has NetMetrix to the same
location on the X display host.
Description Host name resolution can be slow
Symptom Applications appear to hang while processing host names.
Details In some cases, dynamic name resolution (via gethostbyname) works
very slowly. Many of the NetMetrix applications use dynamic name reso-
lution to translate host addresses to “friendly” names. If the resolution is
slow, the application can appear to be frozen.
Work-Around Set the NETM_HOSTMAPX_STATIC_FIRST environment variable to any
value. If this variable exists, NetMetrix first checks the sysnodelist
file, then uses dynamic name resolution. If most or all available host
names are defined in sysnodelist, then using this approach will mini-
mize the problem related to slow name resolution, but dynamic resolu-
tion is still available when needed. Refer to the man pages for
sysnodelist(5) and mkhostdb(1).
Another work-around, if you are not using OpenView, is to turn off
dynamic name resolution completely for NetMetrix by setting the envi-
ronment variable NETM_HOSTMAPX_NO_DYNAMIC to any value. Name
resolution using the static sysnodelist file will continue to function;
however, you may need to update sysnodelist periodically.
Do not set the variable NETM_HOSTMAPX_NO_DYNAMIC if you are using
OpenView. Doing so will prevent some NetMetrix applications from
working properly.
Komentarze do niniejszej Instrukcji