[I think this should be included in the SGI Admin FAQ]
We were having an annoying problem with some SGI machines (mostly "Indy"
models with Sony-made monitors): a number of X11 applications (e.g. Tcl/Tk)
that looked alright on other platforms were displayed using far too big
fonts - even when started remotely on another (non-SGI) host. This rendered
these applications almost unusable on the SGI hosts. It turned out that the
SGI X server was using the 100 DPI fonts instead of the 75 DPI fonts.
For some reason, SGI incorporated some (would-be) heuristics in their
server that tries to calculate the screen resolution at run-time:
-- CUT/BEGIN ---
--- CUT/END ---Quote:> /*
> * XXX MIT specifies misc,Speedo,Type1,NNNdpi,NNNdpi but SGI wants
> * NNNdpi,NNNdpi,misc,Type1,Speedo because of the way the "fixed" font
> * is in NNNdpi instead of being pulled from misc. Also note that Xsgi
> * reorders 100dpi and 75dpi automatically at run-time to best fit
> * the resolution of the actual screen since it varies across monitors
> * and graphics boards.
> #ifndef DefaultFontPath
> #if PrimaryScreenResolution < 88 /* (75 + 100) / 2 */
> #define DefaultFontPath $(FONTDIR)/75dpi/,$(FONTDIR)/100dpi/,$(FONTDIR)/misc/,
> #define DefaultFontPath $(FONTDIR)/100dpi/,$(FONTDIR)/75dpi/,$(FONTDIR)/misc/,
They were so confident with this that they even disabled the "-dpi"
option of the X11 server (Xsgi) [cf. "bugs" section in Xsgi manual page].
If you are using xdm, you can use the following workaround: in
/usr/lib/X11/xdm/Xservers, include the "-fp" (font path) parameter
in the server startup commandline:
--- CUT/BEGIN (one line) --- Also note the "-shnumclients 0" option that works around an Xsgi security You'll have to send the parent xdm a SIGHUP signal (kill -HUP <xdm-pid>) to Enjoy! ;-> Yours truly, Markus B Fleck - CS Student - University of Bonn, Germany - UNIX Support
:0 secure /usr/bin/X11/X -fp /usr/lib/X11/fonts/75dpi/,/usr/lib/X11/fonts/100dpi
-auth .Xauthority -bs -nobitscale -c -pseudomap 4sight -shmnumclients 0 -solidro
ot sgilightblue -cursorFG red -cursorBG white
--- CUT/END ---
bug (cf. Xsgi manual page - it's even documented!).
make xdm reread the Xservers file and use the new settings the next time you
I'm a member of Amnesty International - How about you?
Also note the "-shnumclients 0" option that works around an Xsgi security
You'll have to send the parent xdm a SIGHUP signal (kill -HUP <xdm-pid>) to
Markus B Fleck - CS Student - University of Bonn, Germany - UNIX Support