m1wmk00@fed.frb.gov (William M. Kules) (10/04/90)
Can anyone offer any help on this problem? Please e-mail to me
(wmk@fed.frb.gov or ...!uunet!fed!wmk) if so. This is really
making life miserable. Many thanks -- Bill
CONFIGURATION:
Solbourne 5/602 (a dual-CPU Sparc-based machine)
OS/MP 4.0C (equiv to SunOS 4.0.3)
X11 R4 patchlevel 11
Xdm is controlling 27 NCD 19, 16, and 16e X terminals
SYMPTOMS:
Xdm is forking on the order of 70 times (as shown by lastcomm) per
minute, with each one child proc running about 0.25 seconds. The
login screens appear properly and users are properly logged-in, but
the system is context-switching like crazy, so everything is really
slow.
The loader complains that the revision level of /usr/lib/libX11.so.4.2
is older than expected (3), when first started. (Maybe just a red
herring?)
It generates the following messages repeatedly in the error log
file:
Warning: Cannot convert string "-bitstream-charter-medium-r\
-normal--19-180-75-75-p-106-iso8859-1" to type FontStruct
Error: Unable to load any useable ISO8859-1 font
When debugging is enabled the following messages appear occasionally
in the output (scattered -- not next to eachother):
Display exited with REMANAGE_DISPLAY
Terminating active session for bkancd1:0
Unknown child termination, status <exit status varies>
NOTES:
The font mentioned above _is_ available on the X terminal.
We added new filesystems this morning. One of them was /var/spool.
I don't know of any reason xdm would need to get at /var/spool. Do
you?
-------------------------------------------------------------------------
Bill Kules, Automation and Research Computing | Internet: wmk@fed.FRB.GOV
Federal Reserve Board, Washington, DC | UUCP: uunet!fed!wmk
"Recycling: Just do it, dammit!" | Phone: (202) 452-3933keith@EXPO.LCS.MIT.EDU (Keith Packard) (10/04/90)
> It generates the following messages repeatedly in the error log > file: > Warning: Cannot convert string "-bitstream-charter-medium-r\ > -normal--19-180-75-75-p-106-iso8859-1" to type FontStruct > Error: Unable to load any useable ISO8859-1 font This is caused by a gratuitous change to the X toolkit which occured just before R4 shipped - it used to allow the application to continue by using the default font found in the GC; now the toolkit calls exit when this conversion fails. To circumvent this problem (until R5), find a font which does exist on your X terminal (fixed is a good choice) and add the following line to the Xresources file in the xdm config directory: *XtDefaultFont: fixed You may want to add this line to your own X resources as well, to allow applications which specify non-existant fonts to work against your server.